I too have been facing this issue since a few releases, and still face it on Ubuntu 19.10 (resolvconf not installed as it causes other issues):
# sudo rm /run/systemd/resolve/stub-resolv.conf.tmp # sudo systemctl restart NetworkManager # ls -la /etc/resolv.conf /run/systemd/resolve/ lrwxrwxrwx 1 root root 39 Dec 23 16:31 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf /run/systemd/resolve/: total 8 drwxr-xr-x 3 systemd-resolve systemd-resolve 100 Jan 14 13:01 . drwxr-xr-x 21 root root 480 Jan 14 06:59 .. drwx------ 2 systemd-resolve systemd-resolve 60 Jan 14 13:01 netif -rw-r--r-- 1 systemd-resolve systemd-resolve 613 Jan 14 13:01 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 731 Jan 14 13:01 stub-resolv.conf # nmcli connection up vpn.mydomain.com Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/10) # ls -la /etc/resolv.conf /run/systemd/resolve/ lrwxrwxrwx 1 root root 39 Dec 23 16:31 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf /run/systemd/resolve/: total 16 drwxr-xr-x 3 systemd-resolve systemd-resolve 140 Jan 14 13:01 . drwxr-xr-x 21 root root 480 Jan 14 06:59 .. drwx------ 2 systemd-resolve systemd-resolve 60 Jan 14 13:01 netif -rw-r--r-- 1 systemd-resolve systemd-resolve 613 Jan 14 13:01 resolv.conf -rw-r--r-- 1 systemd-resolve systemd-resolve 731 Jan 14 13:01 stub-resolv.conf -rw------- 1 root root 731 Jan 14 13:01 stub-resolv.conf.pppd-backup.ppp0 -rw-r--r-- 1 root root 753 Jan 14 13:01 stub-resolv.conf.tmp # nmcli connection down vpn.mydomain.com Connection 'vpn.mydomain.com' successfully deactivated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/10) # ls -la /etc/resolv.conf /run/systemd/resolve/ lrwxrwxrwx 1 root root 39 Dec 23 16:31 /etc/resolv.conf -> ../run/systemd/resolve/stub-resolv.conf /run/systemd/resolve/: total 12 drwxr-xr-x 3 systemd-resolve systemd-resolve 120 Jan 14 13:02 . drwxr-xr-x 21 root root 480 Jan 14 06:59 .. drwx------ 2 systemd-resolve systemd-resolve 60 Jan 14 13:01 netif -rw-r--r-- 1 systemd-resolve systemd-resolve 613 Jan 14 13:01 resolv.conf -rw------- 1 root root 731 Jan 14 13:01 stub-resolv.conf -rw-r--r-- 1 root root 753 Jan 14 13:01 stub-resolv.conf.tmp # cat /etc/resolv.conf cat: /etc/resolv.conf: Permission denied # ping -c1 www.google.com ping: www.google.com: Name or service not known # sudo chmod a+r /etc/resolv.conf # ping -c1 www.google.com PING www.google.com (216.58.201.228) 56(84) bytes of data. 64 bytes from par10s33-in-f4.1e100.net (216.58.201.228): icmp_seq=1 ttl=56 time=4.52 ms --- www.google.com ping statistics --- 1 packets transmitted, 1 received, 0% packet loss, time 0ms rtt min/avg/max/mdev = 4.522/4.522/4.522/0.000 ms My work-around is to disable both up and down 0000usepeerdns scripts: # sudo dpkg-divert --divert /etc/ppp/ip-down.d/0000usepeerdns.bak --rename /etc/ppp/ip-down.d/0000usepeerdns # sudo dpkg-divert --divert /etc/ppp/ip-up.d/0000usepeerdns.bak --rename /etc/ppp/ip-up.d/0000usepeerdns -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ppp in Ubuntu. https://bugs.launchpad.net/bugs/1778946 Title: No dns resolution after closing a vpn/pptp connection Status in ppp package in Ubuntu: Fix Released Status in ppp package in Debian: New Bug description: step to reproduce set a VPN connection configured to connect a Microsoft vpn server (pptp) internet acces is ok enable the vpn connection using the applet on the top right corner of the desktop internet still ok ping works disable the vpn connection ping doesn't works with a host but works if i specify an ip address ping: xx.net: Nom ou service inconnu As a workaround, i disable the ethernet link and re-enable it name resolution is now ok ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: network-manager 1.10.6-2ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Jun 27 18:09:30 2018 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2014-06-03 (1484 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) IpRoute: default via 192.168.0.254 dev eth0 proto dhcp metric 20100 169.254.0.0/16 dev eth0 scope link metric 1000 192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.47 metric 100 IwConfig: lo no wireless extensions. eth0 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true RfKill: SourcePackage: network-manager UpgradeStatus: Upgraded to bionic on 2018-05-10 (48 days ago) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eth0 ethernet connected /org/freedesktop/NetworkManager/Devices/2 Connexion filaire 1 94806bba-1c68-46b6-87f4-a3eeeeaff6dd /org/freedesktop/NetworkManager/ActiveConnection/6 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected (site only) started limited enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ppp/+bug/1778946/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
