From: Zbigniew Jędrzejewski-Szmek Date: Thu, 29 Jun 2017 00:43:37 +0000 (-0400) Subject: man: describe the relationship between nss-myhostname and nss-resolved X-Git-Tag: v234~48^2~2 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=2b015ea4b227054dd1c9a60d78e84e0362f1245a;p=platform%2Fupstream%2Fsystemd.git man: describe the relationship between nss-myhostname and nss-resolved Fixes #1605. --- diff --git a/man/nss-resolve.xml b/man/nss-resolve.xml index 4e102ce..51b228f 100644 --- a/man/nss-resolve.xml +++ b/man/nss-resolve.xml @@ -63,13 +63,24 @@ hostnames via DNS. To activate the NSS module, add resolve to the line starting with - hosts: in /etc/nsswitch.conf. Specifcally, it is recommended to place - resolve early in /etc/nsswitch.conf' hosts: line (but + hosts: in /etc/nsswitch.conf. Specifically, it is recommended to place + resolve early in /etc/nsswitch.conf's hosts: line (but after the files or mymachines entries), right before the dns entry if it exists, followed by [!UNAVAIL=return], to ensure DNS queries are always routed via systemd-resolved8 if it is running, but are routed to nss-dns if this service is not available. + + Note that systemd-resolved will synthesize DNS resource + records in a few cases, for example for the localhost and the + current hostname, see + systemd-resolved8 + for the full list. This duplicates the functionality of + nss-myhostname8, + but it is still recommended (see examples below) to keep + nss-myhostname configured in + /etc/nsswitch.conf, to keep those names resolveable if + systemd-resolved is not running.