I was pointed at this bug by Stéphane, and looked again with some extra logging patched in. I'm under the impression that NM is doing exactly as it's told, which also means dnsmasq will do the same: it's simply not configuring a "global" nameserver to go with the per-domain ones.
>From what I can tell after careful testing with the debug logs enabled and watching what NM and dnsmasq say to each other, it looks like this failure scenario happens when you configure the IPv4 settings to "Use this connection only for the resources on its network" (ie. split- tunnelling), but don't enable the same option for the IPv6 settings. That state appears to confuse NM into thinking it shouldn't set the "global" DNS because one of the connections is meant to take the default gateway. I'm still looking at the code to figure out how best to make this work as expected, but I think in the meantime a good workaround would be to mirror the split-tunnelling option in IPv4 and IPv6 settings (the checkbox "Use this connection..."). You may then put IPv6 back to "Ignore" or leave it as-is, since if there are no IPv6 addresses given by the VPN this will simply be ignored. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1603898 Title: DNS resolution fails when using VPN and routing all traffic over it To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1603898/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
