From ce28e6ab3080cacdb1138057ac8442e42e0b20b7 Mon Sep 17 00:00:00 2001 From: Thomas Haller Date: Mon, 14 Nov 2016 12:32:11 +0100 Subject: man: clarify dns=default setting in NetworkManager.conf manual https://bugzilla.gnome.org/show_bug.cgi?id=774399 --- man/NetworkManager.conf.xml | 18 +++++++++++------- 1 file changed, 11 insertions(+), 7 deletions(-) (limited to 'man') diff --git a/man/NetworkManager.conf.xml b/man/NetworkManager.conf.xml index 6df33d4f0b..f765ca9461 100644 --- a/man/NetworkManager.conf.xml +++ b/man/NetworkManager.conf.xml @@ -278,13 +278,17 @@ no-auto-default=* dns - Set the DNS (resolv.conf) processing mode. + Set the DNS (resolv.conf) processing mode. + If the key is unspecified, default is used, + unless /etc/resolv.conf is a symlink to + /run/systemd/resolve/resolv.conf, + /lib/systemd/resolv.conf or + /usr/lib/systemd/resolv.conf. + In that case, systemd-resolved is chosen automatically. + 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 + /etc/resolv.conf to reflect the nameservers + provided by currently active connections. dnsmasq: NetworkManager will run dnsmasq as a local caching nameserver, using a "split DNS" configuration if you are connected to a VPN, and then update @@ -300,7 +304,7 @@ no-auto-default=* manual page for more details). unbound: NetworkManager will talk to unbound and dnssec-triggerd, providing a "split DNS" - configuration with DNSSEC support. The /etc/resolv.conf + configuration with DNSSEC support. /etc/resolv.conf will be managed by dnssec-trigger daemon. systemd-resolved: NetworkManager will push the DNS configuration to systemd-resolved -- cgit v1.2.1