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.
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/NetworkMan ager/NetworkMan ager.conf which is really annoying on a laptop which you move around a lot.