Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: systemd (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.n
I'm having similar problems with DNS resolution in Bionic Ubuntu-Server.
After configuring the netplan file, with the "local" search suffix, name
resolution works, but I see a 5 second delay for any DNS name ending in
.local.
When watching wireshark during the DIG request, the local system makes
Any five second delay in name resolution is most likely caused by this
open bug in systemd-resolved:
https://github.com/systemd/systemd/issues/11849
The root cause is a delay when resolved has to downgrade the feature set
of its requests to upstream DNS servers. It correctly discovers a
compatibl
please reopen if this is still an issue
** Changed in: systemd (Ubuntu)
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1765477
Title:
** Tags added: eoan
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1765477
Title:
5s delay in dns resolving; artful and earlier is quick
Status in systemd package in
I'm seeing this in eoan, too.
Whenever I try to access a host in my lan, host resolution takes 15s
(tried timing "ping -c 1" and "nslookup"
a "dig " query is immediate, but a "dig " also takes
15s.
It seems it's trying 3 times, each with a 5s timeout before failing.
--
You received this b
6 matches
Mail list logo