Friday, 2 December 2016

ANN: network-manager switching from dnsmasq to resolved

Hello all,

In the last cycle we switched DNS resolution for Ubuntu
server/cloud/snappy to resolved according to the "Local DNS resolver
on all Ubuntu installs" spec [2]. This did not yet include
NetworkManager (i. e. desktop images) as until recently there was no
DNS plugin for NM that would talk to resolved [3] and we had an old NM
version.

Now we have 1.4 in zesty and NM grew a resolved DNS plugin, so I
backported it into our version and switched it on.

This now means that everything in Ubuntu uses the same mechanism, and
we stop having two DNS resolvers running on desktops. I gave this a
fair round of testing, but of course there is always the possibility
that this breaks stuff. If you find a regression, please file a bug
against network-manager and subscribe me.

In the worst case, these are the two commits to revert to undo this:

https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=98974a88
https://git.launchpad.net/~network-manager/network-manager/+git/ubuntu/commit/?id=47c16e59

Thanks,

Martin

[1] https://lists.ubuntu.com/archives/ubuntu-devel/2016-May/039350.html
[2] https://blueprints.launchpad.net/ubuntu/+spec/foundations-y-local-resolver
[3] This is necessary as information like "use this DNS server for
these domains or on this interface only" cannot be conveyed via
/etc/resolv.conf.

--
Martin Pitt | http://www.piware.de
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)

--
ubuntu-devel mailing list
[email protected]
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-devel