[Bug 1624317] Re: systemd-resolved breaks VPN with split-horizon DNS

[Tim Shannon]

The DNS servers have always been listed under the vpn0 link when I run
systemd-resolve --status, even before your patch.

I still get no internal network name resolution, even when hard coding
the DNS servers in network manager.

Maybe I've got a different issue than what others are seeing, but I have
confirmed that on 16.10 the vpn works correctly, resolves internal
names, and doesn't leak, but on 17.04 it no longer works.

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, 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 network-manager package in Ubuntu:
  Confirmed
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