> I want to be clear that in my situation the VPN’s DNS servers are
_not_ marked as domain-restricted.
This is something different then; dropping the upstream bug link. So I'm
afraid this needs a more precise description of how to set this
up/reproduce this, and a debug output of resolved would be helpful:
sudo systemctl stop sytemd-resolved
sudo SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-resolved
then do the operation that fails, and copy&paste the output here.
Thanks!
** Changed in: systemd
Importance: Unknown => Undecided
** Changed in: systemd
Remote watch: github.com/systemd/systemd/issues #3421 => None
** Changed in: systemd (Ubuntu)
Status: Triaged => Incomplete
--
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:
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
--
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
