Comment 13 for bug 1629611

Revision history for this message
Thomas M Steenholdt (tmus) wrote :

Wow - Long message, but what I got from it was "I need to see a debug log", correct? I'll attach that...

I'll also point you to the problematic part:

Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1915] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "workdom.lan"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1915] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "22.60.10.in-addr.arpa"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@vpn0' for domain "23.60.10.in-addr.arpa"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "workdom.lan"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "22.60.10.in-addr.arpa"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@vpn0' for domain "23.60.10.in-addr.arpa"
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1916] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.48@enp0s31f6'
Dec 5 15:14:48 bar14860 NetworkManager[921]: <debug> [1480961688.1917] dnsmasq[0x560b551920f0]: adding nameserver '10.60.180.49@enp0s31f6'

Now for this test, I'm using the same DNS before and after, but the VPN connection adds DNS resolution using the VPN provided DNS ONLY for the domains it feels is behind the VPN, and there's nothing I can seemingly do to change that behaviour. This is the exact assumption that breaks VPN for many users. When I connect to VPN, especially one that becomes my default gateway, I need all DNS requests to go the the DNS servers behind the VPN.

Need more info, let me know.