Ubuntu
network-manager package

DNS fails after reconnecting to a VPN

Bug #1671964 reported by Cédric M. Campos
24
This bug affects 5 people
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Since update 1.2.2-0ubuntu0.16.04.3 of network-manager, when I reconnect (i.e. connect, disconnect, connect) to a VPN (OpenVPN), DNS resolution stops working.

Workaround: systemctl restart NetworkManager

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Ryan Stark (rstark) wrote :

Restarting NetworkManager didn't work for me. DNS lookups for my network would fail REFUSED if queried against 127.0.1.1(dnsmasq) but work fine if I queried google's dns 8.8.8.8.

What did work was to modify the VPN connection and change the ipv4 configuration to address only, then manually add the routes I needed for the VPN (I did a broadstroke and routed 10.0.0.0/8 to the vpn tun)

Revision history for this message
dlotton (yellow56) wrote :

I have a similar problem. I tried rolling back the network manager from 1.2.6-0ubuntu0.16.04.1 to 1.2.2-0ubuntu0.16.04.4. Oddly, it seemed to fix DNS for a few minutes, but it reverted to not working.

I noticed that a few days before the network manager was updated resolvconf also updated. I believe resolvconf is responsible for notifying applications (like the local resolver) when something like a DHCP lease gets established and a new DNS server is needs to be pointed to.

I downgraded resolvconf from 1.78ubuntu4 to 1.78ubuntu2 and this seems to have fixed my problem.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.