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

[Anders Kaseorg]

Public bug reported:

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

** Affects: systemd (Ubuntu)
     Importance: Undecided
         Status: New

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

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/ubuntu/+source/systemd/+bug/1624317/+subscriptions