After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 782597 - DNS and search domain is not pushed to systemd-resolved sometimes
DNS and search domain is not pushed to systemd-resolved sometimes
Status: RESOLVED DUPLICATE of bug 779087
Product: NetworkManager
Classification: Platform
Component: IP and DNS config
1.4.x
Other Linux
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-05-13 15:50 UTC by andysem
Modified: 2017-05-19 08:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
NetworkManager and systemd-resolved log (14.19 KB, application/x-xz)
2017-05-13 15:50 UTC, andysem
Details

Description andysem 2017-05-13 15:50:12 UTC
Created attachment 351782 [details]
NetworkManager and systemd-resolved log

I have an OpenVPN connection with statically configured DNS server address and the search domain. When this connection is established, there is a high chance that the DNS address and the search domain are not pushed to systemd-resolved for this connection. The problem does not reproduce reliably, sometimes the parameters are pushed. When the parameters are not pushed, 'systemd-resolve --status' reports no DNS servers or DNS domain for the VPN connection, and name resolution does not work.

I'm attaching NetworkManager and systemd-resolved logs where the connection is established and teared down twice. The first time DNS parameters were not pushed to systemd-resolved, the second time they were. You can see a log record from systemd-resolved is only present when the connection is set up the second time.

ipv4 section for the VPN connection looks like this:

[ipv4]
dns=10.0.7.10;
dns-search=mcdlabs.net;
ignore-auto-dns=true
method=auto
never-default=true

I'm on Kubuntu 17.04, x86_64, NetworkManager 1.4.4.
Comment 1 Beniamino Galvani 2017-05-19 08:21:02 UTC
The first time tun0 is not yet managed by NM and so its configuration is ignored by the resolved DNS plugin; this is a duplicate of bug 779087.

Please try NM 1.8 or backport commit:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=913896721d7c7c65f7e4a24e8c0d9d275a9dfbaa

*** This bug has been marked as a duplicate of bug 779087 ***