Just found this article https://github.com/systemd/systemd/issues/5755
Following the argument, systemd-resolved resolves DNS names on the assumption that all configured DNS servers are equal. diego-treitos and others argue that in small/medium sized companies, DNS configuration will have an external DNS server configured and conveyed via DHCP. This is the case here as well. This has not posed a problem before systemd-resolved was adopted. But when a resolver insists on treating the fallback equally and keeping the connection till the next fallback, internal DNS resolution is not possible any more. It breaks known and established configurations. I have to accept that RFCs actually lend to the interpretation of poettering. In this case (as he is reluctant to adapt his softwares behaviour to previously known standards) there need to be a quick way to eliminate systemd-resolver from the system. I for one need the old behaviour with a primary DNS (internal, it resolved private addresses as well) and a secondary DNS (external, which only resolved external / official addresses) as a fallback. ** Bug watch added: github.com/systemd/systemd/issues #5755 https://github.com/systemd/systemd/issues/5755 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1718890 Title: name resolution stops working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1718890/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
