1) Add an openvpn connection, which emits DHCP DNS servers, and is flagged "use only for resources on this connection" 2) Add a negative dns_priority to the connection via CLI or editing the connection
Prior to the change, this worked fine, you could connect, and the indicated DNS server would become prioritised. After the change, this no longer works, and networkmanager will not associate a DNS server to the connection at all. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1851407 Title: NetworkManager 1.10.6-2ubuntu1.2 breaks VPN DNS Status in network-manager package in Ubuntu: Confirmed Bug description: NetworkManager as of 1.10.6-2ubuntu1.2 has cause a regression whereby a VPN connection which sets it's dns-priority to a negative value, which should cause the DNS server supplied by the DNS connection to be placed first, instead now refuses to place the DNS server into the resolver under any circumstance. Pinning the 1.10.6-2ubuntu1.1 works around the issue. I suspect the fix-dns-leak-lp1754671.patch has caused this regression. This patch should be reverted as soon as possible to restore proper functionality of network manager with respect to VPN servers with DNS resolvers. $ lsb_release -rd Description: Ubuntu 18.04.3 LTS Release: 18.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1851407/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
