I first experience this issue with nm version 1.8.2-1ubuntu1 in an - as of writing fully updated - 17.04.
Syslog will be attached, from that you can see that dnsmask gets the nameserver, networkmanager gets it too, but it doesn't make to resolv.conf, that will only have the stub resolver. /etc/resolv.conf is a link ending in /run/resolvconf/resolv.conf. Workaround is to manually add the nameserver to resolv conf and comment out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf which is really annoying on a laptop which you move around a lot. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1568787 Title: resolvconf does not reliable receive nameserver information from NetworkManager To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1568787/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
