You can still add the vpn nameserver to /etc/resolv.conf . Epic blunder by both systemd-resolv maintainer and Ubuntu packagers for stacking a broken configuration together for at the 3rd release. Does anyone know how to escalate this?
On May 4, 2017 19:04, "Winckler" <winck...@campogeral.com.br> wrote: > It's a really ugly workaround, but I'm using iptables to block > connections to my ISP's DNS. I manually create and remove iptables rules > using a script but at least this allows me to work remotely. I hope this > get fix soon. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1624317 > > Title: > systemd-resolved breaks VPN with split-horizon DNS > > Status in systemd: > New > Status in systemd package in Ubuntu: > Confirmed > > Bug description: > I use a VPN configured with network-manager-openconnect-gnome in which > a split-horizon DNS setup assigns different addresses to some names > inside the remote network than the addresses seen for those names from > outside the remote network. However, systemd-resolved often decides > to ignore the VPN’s DNS servers and use the local network’s DNS > servers to resolve names (whether in the remote domain or not), > breaking the split-horizon DNS. > > This related bug, reported by Lennart Poettering himself, was closed > with the current Fedora release at the time reaching EOL: > https://bugzilla.redhat.com/show_bug.cgi?id=1151544 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/systemd/+bug/1624317/+subscriptions > -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1624317 Title: systemd-resolved breaks VPN with split-horizon DNS Status in systemd: New Status in systemd package in Ubuntu: Confirmed Bug description: I use a VPN configured with network-manager-openconnect-gnome in which a split-horizon DNS setup assigns different addresses to some names inside the remote network than the addresses seen for those names from outside the remote network. However, systemd-resolved often decides to ignore the VPN’s DNS servers and use the local network’s DNS servers to resolve names (whether in the remote domain or not), breaking the split-horizon DNS. This related bug, reported by Lennart Poettering himself, was closed with the current Fedora release at the time reaching EOL: https://bugzilla.redhat.com/show_bug.cgi?id=1151544 To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1624317/+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
