I've now got one instance with this condition again. >From what I can see from the logs is that systemd-resolved started using some >other DNS server: First one in my network where I do not have control over (ipv4: 192.168.178.1 , somehow it turned up with this fairly correct address : my router) Then one which I do not know at all (ipv6: fd00::464e:6dff:fefb:1b50 , don't know where that is)
What I would like is to have it stick to 192.168.178.2 , which is used to supply addresses to virtual machines. I'll leave systemd-resolved running as is for now for inspection. Aug 18 12:09:38 kvm1804 systemd-resolved[2418]: Switching to DNS server 192.168.178.1 for interface br0. ... Aug 18 12:56:15 kvm1804 systemd-resolved[2418]: Switching to DNS server fd00::464e:6dff:fefb:1b50 for interface br0. -- 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
