Comment 13 for bug 1636395

Hi,

I'm having exactly the same problem as described by @raffraffraff - after connection to the VPN the dnsmasq instance handled by NetworkManager no longer makes DNS queries for addresses outside the VPN (eg. google.com) but it can resolve ones internal to the VPN (eg. web-dev.myorg.private).

Using DIG to make a direct DNS query to any remote DNS server works fine, so it looks like dnsmasq has got in a tizz.

To add a little more info...

I'm able to add a file /etc/NetworkManager/dnsmasq.d/debug containing the line "log-queries" and I can see lines in syslog like:

... dnsmasq[25056]: forwarded www.google.com to 129.215.205.191

So obviously dnsmasq is trying to process the requests but failing.

I can also see dnsmasq picking up new configurations from DBUS as I connect/disconnect but there are no errors reported.

I also note that dnsmasq is trying to make queries via the public DNS servers, but when connected to the VPN all the queries should go to the trusted DNS server provided on the VPN (this is discussed in bug 1639776) but I think this is a separate issue.

Ubuntu 16.04.2 LTS
dnsmask-base 2.75-1ubuntu0.16.04.2
network-manager 1.2.6-0ubuntu0.16.04.1

Cheers,

TIM