As explained, 127.0.0.53 must be in /etc/resolv.conf in order to support
Chromium and other software which does not NSS -- that is the whole
raison d'être for providing a local stub server.
In Yakkety with NetworkManager only the 127.0.1.1 dnsmasq server is in
/etc/resolv.conf, so that isn't affected. In Zesty NM now does not
manager resolv.conf itself any more but just sends the acquired name
servers to resolved.
Thus, is there anything left from the original bug report that still
needs to be addressed?
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
** Tags added: resolved
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1624320
Title:
systemd-resolved appends 127.0.0.53 to resolv.conf alongside existing
entries
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1624320/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
