The submitter Oscar wrote in the original description: > If I comment out dns=dnsmasq in NetworkManager.conf and > restart NetworkManager all DNS start to work properly again, > VPN DNS's are used for those resources on the VPN network > and others through my default DNS.
Oscar, I don't know how that could be the case. The glibc resolver does not route DNS queries according to the name looked up. The resolver just tries one nameserver, waits the timeout period, then tries another nameserver, etc., until it receives an answer. VPN nameservers are often set up to resolve Internet names as well as names on the remote LAN. That may have been true in your case. Oscar wrote in comment #1 > Forgot to add, setting the name servers manually under > Additional name servers in Network Manger GUI setting > still doesn't acyually add the name servers I can confirm this. This may be bug #1072899 again. To everyone who has a malfunction and solves it by commenting out "dns=dnsmasq": perhaps you are hitting bug #1003842. Also make sure that /etc/resolv.conf is a symbolic link to ../run/resolvconf/resolv.conf. To Hans, who worked around his bug by removing resolvconf: you probably had a different problem and removing resolvconf fixed it as a side- effect. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1169437 Title: network-manager dnsmasq openvpn DNS issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1169437/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
