Ubuntu
resolvconf package

  1. Bug #994575
  2. Comment #10

Comment 10 for bug 994575

Revision history for this message
Brian Marks (c-brian-marks) wrote : Re: dnsmasq does not update nameserver info after network change

Okay, Thomas, I've done some more testing based on your response in #9. I'd be interested to hear your opinion on what may be going on. Here's the results...

TESTING WITH DNSMASQ DISABLED
I disabled dnsmasq in /etc/NetworkManager/NetworkManager.conf by commenting out the dnsmasq setting like:
#dns=dnsmasq

Then restarted networkmanager using the command:
sudo restart network-manager

After that, connected to VPN with DNS servers and search domains specified in VPN settings. /etc/resolv.conf does not contain the VPN DNS servers. The only one listed is 127.0.0.1. The search domains are listed though. The VPN DNS servers are in /var/run/resolvconf/interface/NetworkManager and /var/run/resolvconf/interface/ppp0. Running host command without specifying VPN DNS still does not resolve - "Host {myhost} not found: 3(NXDOMAIN)".

TESTING WITH DNSMASQ ENABLED
Re-enabled dnsmasq in /etc/NetworkManager/NetworkManager.conf. "dns=dnsmasq"
Restarted networkmanager

"nameserver 127.0.0.1" only DNS server in /etc/resolv.conf as expected.
/var/run/nm-dns-dnsmasq.conf file does not exist. <-- This could be the problem.
Any ideas on why this file is not being created? Could it be a permission issue?

Should I be posting this in bug #1003842 instead? Is what I'm doing helpful?