Looks like the DNS provided by Cloudflare (1.1.1.1 and 1.0.0.1) has picked up with standards and is also delivering NXDOMAIN together with an authority section with a SOA when you query anything in local.
. 86400 IN SOA a.root-servers.net. nstld.verisign-grs.com. 2021112100 1800 900 604800 86400 Hence also cloudflare is now unusable with the default configuration of ubuntu 20.04 because it ends up breaking local name resolution via mDNS. This follows from the fact that ubuntu focal relies on systemd-resolved by default and uses version 245.4 which is broken as per this bug (and also unsupported by upstream that would like not to be questioned for anything apart the last two versions). I have been pointed to a PPA providing daily builds of systemd, but obviously replacing your init system daily with the associated risk of breaking boot and not being able to access apt to restore the system is not feasible outside of a test-and-throw-away virtual machine. Please, try to have this bug fixed, because having a broken DNS stub resolver by default is a bit of a pain. If possible, also try to (downstream) decouple initialized services from init supervision itself so that when a service like systemd-resolved reveals an issue it is possible to try addressing it without having to replace the whole of the init system — risking serious system breakage — or without having to move to a different codebase to provide the same or a similar service — overriding the system default. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1950850 Title: Systemd-resolved gets confused and replies to SOA queries for local breaking mDNS resolution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1950850/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
