This bug was fixed in the package network-manager - 1.4.2-2ubuntu4
---------------
network-manager (1.4.2-2ubuntu4) zesty; urgency=medium
[ Martin Pitt ]
* Add resolved DNS plugin (backported from upstream master).
* Disable resolvconf support.
This is broken with DNS plugins other than "dnsmasq" -- it still writes
127.0.1.1 into resolvconf as a nameserver, but this does not exist any more
and
will also shadow resolved's stub server on 127.0.0.53.
This ought to be fixed more properly in the future.
[ Steve Langasek ]
* Re-drop dnsmasq in zesty, in favor of systemd-resolved.
This unifies DNS lookups between Ubuntu desktop and server.
But don't Recommend libnss-resolve, because the local resolver +
libnss_dns.so
should suffice for all uses and the resolved nss module is unnecessary added
complexity.
We need to specify "dns=systemd-resolved" as for the time being our
/etc/resolv.conf points to resolvconf's generated file instead of
systemd-resolved's, so the auto-detection does not work. Do that in a
separate conf.d file in /usr to avoid unnecessary conffile prompts in the
future. The user can still override it in /etc. (LP: #1638836)
-- Martin Pitt <martin.p...@ubuntu.com> Fri, 02 Dec 2016 09:36:02
+0100
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1638836
Title:
resolv.conf for resolved stub server should have a comment how to see
the actual servers
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638836/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
