What type of VPN connection are you using? I am using network-manager-openvpn, and it has the opposite behavior (I can only get it to append a new DNS server to the list reported by `systemd-resolve --status`, while in my case, I would like network- manager to *only* use the VPN DNS).
The change in behavior between systemd-resolved and glibc resolvconf is nontrivial, and has side effects throughout various parts of the system. In this case, it appears that various developers have implemented different defaults for different protocols. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1768203 Title: Connecting to a VPN clears DNS from parent connection Status in network-manager package in Ubuntu: New Bug description: $ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 $ apt-cache policy network-manager network-manager: Installed: 1.10.6-2ubuntu1 Candidate: 1.10.6-2ubuntu1 Version table: *** 1.10.6-2ubuntu1 500 500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages 100 /var/lib/dpkg/status After connecting to a VPN the parent connection's DNS servers are cleared, as seen in the output of `systemd-resolve --status`. Before connection to VPN: (...) Link 3 (wlp2s0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 62.179.1.63 62.179.1.62 DNS Domain: chello.pl Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Connected to VPN, notice that only the ppp0 has DNS servers: (...) Link 20 (ppp0) Current Scopes: DNS LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no DNS Servers: 192.168.64.5 192.168.97.10 DNS Domain: ~dcs.pl Link 3 (wlp2s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no Link 2 (enp1s0) Current Scopes: none LLMNR setting: yes MulticastDNS setting: no DNSSEC setting: no DNSSEC supported: no I want to use split-horizon DNS resolving, and this behaviour breaks resolving non-VPN names. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1768203/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
