Issues related to the yakkety switch to systemd-resolved

[Joe Barnett]

Hello,

Posting in response to the old thread in ubuntu-devel titled "ANN: DNS
resolver changes in yakkety", but since that thread is several months old,
thought I'd start a new one.

Since upgrading to yakkety, I've noticed the following issues seemingly
related to (a partial?) switch to systemd-resolved for DNS:

1)  The first issue I noticed was that when connected to an openvpn VPN,
firefox stopped being able to resolve DNS entries from the VPN's DNS
server, while command line tools (host/ping) worked fine.  Traced this down
to two things, both seemingly related to my former use of resolvconf not
fully migrating over to use systemd-resolved:
    a) Had to change my .ovpn file to point to
/etc/openvpn/update-systemd-resolved
instead of /etc/openvpn/update-resolv-conf
    b) Had to change my /etc/resolv.conf to point to
/lib/systemd/resolv.conf instead of /run/resolvconf/resolv.conf
   Reading the documentation, it appears that systemd-resolved should have
been reading from the resolvconf managed /etc/resolv.conf, but that appears
to not have been happening?

2) After a suspend/resume cycle, DNS queries stopped working unless I
restarted network-manager: https://bugs.launchpad.net/
ubuntu/+source/network-manager/+bug/1629620
    a) After doing the fixes for problem #1, this appears to be working
better now

3) Steam was unable to see the network: https://bugs.launchpad.net/
ubuntu/+source/steam/+bug/1631980
    a) After manually installing libnss-resolve:i386, this is now resolved,
but should this package have been installed automatically when
libnss-resolve:amd64 was installed?

4)  Virtualbox hosted windows VM unable to see the network when in NAT
mode: https://bugs.launchpad.net/ubuntu/+source/virtualbox/+bug/1632084
    a) this is still unresolved


Anyways, assuming there's eventually a fix found for #4, my real question
is not so much that there were bugs, but rather are there still changes
that should be made to make the solution for these issues more automatic
(ie, automatically apply 1.b and 3.a)?  Or at least to notify the user more
loudly that their configuration is not fully supported?

Thanks,
-Joe
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/ubuntu-devel-discuss/attachments/20161018/4ee3cd11/attachment.html>