Ubuntu
resolvconf package

  1. Bug #994575
  2. Comment #9

Comment 9 for bug 994575

Revision history for this message
Thomas Hood (jdthood) wrote : Re: dnsmasq does not update nameserver info after network change

Brian Marks wrote:
> Yes, tried restarting network-manager but used UI 'enable
> networking' checkmark to disable and re-enable.  Would this be
> consistent with using command line to restart service?

Using the indicator to dis-"Enable Networking" and re-"Enable Networking" does not restart the NetworkManager daemon, which is necessary for changes to /etc/NetworkManager/NetworkManager.conf to become effective. You have to open a Terminal and do "sudo restart network-manager" or reboot.

> I have reviewed the resolv.conf file before and after connecting and the
> problem appears to be that the VPN DNS servers are not getting added to
> the file although search domains are getting added.

Well, when NM is in "dns=dnsmasq" mode you will only see "nameserver 127.0.0.1" in /etc/resolv.conf. No further addresses will be added there. The addresses of the upstream nameservers including the VPN ones should appear in /var/run/nm-dns-dnsmasq.conf instead.

If you comment out "dns=dnsmasq" in /etc/NetworkManager/NetworkManager.conf and restart network-manager then up to three upstream nameserver addresses will be included directly in /etc/resolv.conf and there will be no /var/run/nm-dns-dnsmasq.conf file.

If, in either case, you don't see your VPN nameserver addresses in the appropriate file then there is something wrong with, e.g., your DHCP server configuration, DHCP client, ....

But I suspect that you have also hit #1003842 and that you will find that everything works after you restart network-manager with "dns=dnsmasq" commented out.