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

[Martin Pitt]

Note that in current Yakkety, NetworkManager uses dns=dnsmasq again,
because until two weeks ago there was no resolved plugin for
NetworkManager. That exists upstream now, but not yet in our packages,
thus resolved only learned about these via dhcp-client writing the
nameservers into /etc/resolv.conf and thus any association of name
servers to their corresponding links was lost.

This will be fixed by the resolved plugin when NM can tell resolved
about per-link DNS servers.

I think this might actually be what you mean with "split-horizon DNS".
If it is, then this is fixed in yakkety, and will be fixed in z-series
by using the resolved DNS plugin. If not, I don't know what you mean I'm
afraid.

-- 
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 systemd package in Ubuntu:
  Incomplete

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