*** This bug is a duplicate of bug 1003842 ***
https://bugs.launchpad.net/bugs/1003842
Thomas:
After doing some more research I found what was causing the VPN DNS resolution
in my specific scenario. Based on some comments in bug #959037, I found that
the bind9 service was installed and running. After uninstalling bind9 using
synaptic and restarting the networkmanager service, name to IP resolution began
working. Also the file /var/run/nm-dns-dnsmasq.conf showed up and was being
correctly populated.
Here's what my config files look like now with VPN connection (edited to
protect company security). Based on your prior response, I'm confused
as to why resolv.conf has more than just the loopback IP. It works,
though.
/etc/resolv.conf:
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver {first vpn dns IP addr in network manager}
nameserver {second vpn dns IP addr in network manager}
nameserver 127.0.0.1
search {first vpn search domain in network manager} {second vpn search domain
in network manager}
/var/run/nm-dns-dnsmasq.conf:
server={first vpn dns IP addr in network manager}
server={second vpn dns IP addr in network manager}
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/994575
Title:
dnsmasq does not update nameserver info after network change
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/994575/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
