> The local systemd-resolved fails to resolve the name so client applications return failures. Most notably it shows up in web browsers but also for apt package updates.
still not following you on why it's causing systemd-resolved to fail to resolve the name. the new socket graveyard helps avoid sending icmp errors to upstream nameservers, when resolved is performing a lookup to multiple nameservers in parallel. it should make no difference to the local client that just wants to know the details of the dns lookup. maybe it would help if you gave more details about how to reproduce the actual local dns lookup failure. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1940908 Title: resolved: closes listening socket too rapidly and sends Destination port unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1940908/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
