This still happens on network-manager 0.9.4 on precise pangolin... the dnsmasq configuration isn't set to "all servers", so dnsmasq picks the original one outside the VPN, making hosts inside the VPN inaccessible.
-- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/898224 Title: Wrong dnsmasq configuration when VPN is set as default gateway Status in “network-manager” package in Ubuntu: Fix Released Bug description: When using dnsmasq with Network Manager (DNS=dnsmasq in the config) and a VPN that's not configured as "Use VPN only for resources on its network" (default configuration), the dnsmasq configuration ends up being wrong. I'd have expected the default DNS server to be the one received from the VPN connection instead of the one from the current wired/wireless network as that one isn't reachable. So in a setup where VPN doesn't provide the default gateway, DNS should be: - DNS queries for anything on the VPN network => DNS server from VPN - Everything elsse => DNS server from current wired/wireless network In a setup where the default gateway is the VPN - Everything => DNS server from VPN To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/898224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
