192.168.178.1 was defined as secondary nameserver on kvm1804 within 01-netcfg.yaml (ubuntu 18.04).
The primary nameserver is just operating properly. I do not see any reason why systemd-resolved would not target this primary nameserver, let alone target something external to me at all. In case of emergency it might use a subsequent nameserver, but it should switch back when possible. To my knowledge the primary nameserver did not have any problems during these switches. This machine has a static ip address, it is a physical machine running virtuals. I've seen "Switching to DNS server" logged on desk-02 (ubuntu 20.04.1) for which I filed this bug. This directly switched to the external ipv6 fd00::464e:6dff:fefb:1b50. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1890903 Title: systemd-resolved.service still breaks (now 20.04, since as least 16) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1890903/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
