To confirm again:
$ systemd-resolve --status | grep "Current DNS" -A 2 -B 1
DNSSEC supported: no
Current DNS Server: 192.168.1.1
DNS Servers: 192.168.1.1
DNS Domain: ~.
This remains true even if I manually force the right DNS in the VPN
settings.
Attaching syslog of a split connection being established, with correctly
reports receiving the right DNS from the VPN server, but still obtains
the same result at systemd level.
** Attachment added: "vpn connection - syslog.log"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+attachment/5384648/+files/vpn%20connection%20-%20syslog.log
--
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/1829838
Title:
1.10.14-0ubuntu2 breaks DNS propagation from VPN
Status in network-manager package in Ubuntu:
Confirmed
Bug description:
I have an OpenVPN connection, and I use the update-systemd-resolved to
correctly fetch the DNS from the VPN. The issue arose updating my
Ubuntu 18.04: the script is no longer invoked, and even invoking it
manually (sudo openvpn myfile.ovpn) does not work anymore, even if in
that case systemd-resolve --status shows the new DNS on the interface
correctly.
As suggested in https://bugs.launchpad.net/ubuntu/+source/network-
manager/+bug/1211110/comments/99, reverting to 1.10.6-2ubuntu1.1 fixes
the issue.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1829838/+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
