Comment 9 for bug 1592721

I think I am observing a regression caused by this fix: after disconnecting/reconnecting a VPN connection, DNS resolution is broken. Here are the details:

- VPN is set up as OpenVPN with split-tunneling ("Use this connection only for resources on its network" is checked). The VPN's DNS domain is ozone.caligrafix.cl, and the DNS server is 192.168.0.2. The local (non-VPN) DNS server is 192.168.50.2.

- Right after boot, and after connecting to the VPN for the first time, I can ping a host on the VPN's network (ping somehost.ozone.caligrafix.cl)

- If I disconnect and reconnect to the VPN, I cannot ping the same host by name (I get Name or service not known). I can ping it by IP.

Strangely enough, dnsmask says it does use the VPN's resolver, as shown by this syslog extract:

Nov 1 23:09:28 tadzim3 dnsmasq[1671]: setting upstream servers from DBus
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.50.2#53(via wlan0)
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for domain ozone.caligrafix.cl
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for domain 1.8.10.in-addr.arpa
Nov 1 23:09:28 tadzim3 dnsmasq[1671]: using nameserver 192.168.0.2#53 for domain 0.168.192.in-addr.arpa
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: reading /etc/resolv.conf
Nov 1 23:09:28 tadzim3 dnsmasq[1450]: using nameserver 127.0.1.1#53
^C
gpothier@tadzim3:~$ ping somehost.ozone.caligrafix.cl
ping: somehost.ozone.caligrafix.cl: Name or service not known