I examined the differences between bionic and upstream NetworkManager source around systemd-resolved interactions. I did not see any significant differences to blame for this.
I have just tested it on a build from nm-1-10 branch of upstream NetworkManager and the behavior seems to be identical: the DNS for VPN is lost. This looks like an upstream issue. I will do more testing to confirm. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1851793 Title: NetworkManager OpenVPN No longer sets up DNS if "Use this connection only for resources on its network" is ticked Status in network-manager-openvpn package in Ubuntu: Incomplete Bug description: Hi, after recent update few days ago, I noticed that DNS is not configured if "Use this connection only for resources" on its network is ticked, for OpenVPN, which used to work till latest update. My config: - IPv4 Method: Automatic (DHCP) - DNS: 10.1.0.1, Automatic: Off - Routes: Automatic: On - [x] Use this connection ... If OpenVPN is setup to work for all resources, then DNS is configured properly. It would be nice if DNS is also configured as before. BR Uros Description: Ubuntu 18.04.3 LTS Release: 18.04 network-manager-openvpn: Installed: 1.8.2-1 Candidate: 1.8.2-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1851793/+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
