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 774399 - man: clarify dns=default regarding systemd-resolved
man: clarify dns=default regarding systemd-resolved
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: Documentation
git master
Other All
: Normal normal
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2016-11-14 11:14 UTC by Marcos Mello
Modified: 2016-11-14 15:36 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Marcos Mello 2016-11-14 11:14:04 UTC 
NetworkManager.conf(5) says for dns=default:

default: NetworkManager will update resolv.conf to reflect the nameservers provided by currently active connections. This is the default if the key is not specified, unless the system is configured to use systemd-resolved; in this case the default is systemd-resolved

"unless the system is configured to use systemd-resolved" needs a better explanation.

If I got right what the code does, this would make things clearer:

default: NetworkManager will update resolv.conf to reflect the nameservers provided by currently active connections. This is the default if the key is not specified, unless the system is configured to use systemd-resolved (resolv.conf is a symlink to /run/systemd/resolve/resolv.conf, /lib/systemd/resolv.conf, or /usr/lib/systemd/resolv.conf); in this case the default is systemd-resolved
Comment 1 Thomas Haller 2016-11-14 11:46:20 UTC 
is this better: https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=ce28e6ab3080cacdb1138057ac8442e42e0b20b7 ?


(closing as fixed, please reopen if it's still wrong).

Thanks
Comment 2 Marcos Mello 2016-11-14 15:36:32 UTC 
Much better! Thanks.