DNS Settings for VPN connections don't work for split tunnel settings

[Catscrash]

Hi,

with the update from 18.04 to 19.04 the network-manager stopped being able to set DNS settings for VPN connections where the checkbox "use this connection only for resources on its network" is not checked.

Without the checkbox:
Link 17 (tun0)
      Current Scopes: DNS
DefaultRoute setting: yes
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no
  Current DNS Server: 192.168.xx.xx
         DNS Servers: 192.168.xx.xx
                      192.168.xx.xx
          DNS Domain: ~.

with the checkbox set:
Link 18 (tun0)
      Current Scopes: none
DefaultRoute setting: no
       LLMNR setting: yes
MulticastDNS setting: no
  DNSOverTLS setting: no
      DNSSEC setting: no
    DNSSEC supported: no

Nothing else - other than this checkbox changed.

Unfortunately without the checkbox I lose my internet connection, as this VPN is not set up to forward internet.

ii network-manager 1.16.0-0ubuntu2
ii network-manager-openvpn 1.8.10-1
ii network-manager-openvpn-gnome 1.8.10-1
ii openvpn-systemd-resolved 1.2.7-1

Thanks!

[Till Kamppeter (till-kamppeter)]

Could you uninstall openvpn-systemd-resolved with

sudo apt purge openvpn-systemd-resolved

and then reboot?

The openvpn-systemd-resolved is actually not needed for network-manager with systemd-resolved in Ubuntu.

Does this solve your problem?

If not, please run the command

systemd-resolve --status

for both cases and post the full output here.

Also provide a debug log of Network Manager for both cases following the instructions on

https://wiki.ubuntu.com/DebuggingNetworkManager

and attach the resulting files here. Please do not compress the files and do not package them together.

[Launchpad Janitor (janitor)]

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]