GNOME Bugzilla – Bug 779087
VPN DNS servers discarded when using systemd-resolved DNS
Last modified: 2017-05-19 08:21:02 UTC
In Ubuntu 17.04 (Zesty Zapus) NetworkManager has switched from DNSMasq to Systemd-resolved for DNS. Unfortunately this broke DNS resolution on my VPN connection. I'm using the network-manager-l2tp VPN plugin. After investigating - it seems the VPN connection's DNS server information is discarded when using the systemd-resolved DNS plugin. Since the PPP interface the VPN creates is not "managed" by NetworkManager, the systemd-resolved plugin ignores DNS servers from that interface entirely. https://github.com/NetworkManager/NetworkManager/blob/44ecb41/src/dns/nm-dns-systemd-resolved.c#L121 The DNSMasq plugin does not exibit this issue since it does not check if the interface is managed. It's my belief that the Systemd-Resolved plugin should follow the older DNSMasq's precedent and add all known DNS servers even if the interface is unmanaged.
Created attachment 346637 [details] [review] [PATCH] dns/resolved: consider configuration from unmanaged devices (In reply to Daniel Ramos from comment #0) > It's my belief that the Systemd-Resolved plugin should follow the older > DNSMasq's precedent and add all known DNS servers even if the interface is > unmanaged. Yes, makes sense. Patch attached.
lgtm
Applied to master: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa and nm-1-6: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-6&id=f950df775f6e71d20d3a912da8a92b3d0095a9b6 Thanks for reporting this.
*** Bug 782597 has been marked as a duplicate of this bug. ***