diff options
author | plattrap <plattrap@yahoo.com> | 2021-06-18 12:32:02 +1200 |
---|---|---|
committer | Yu Watanabe <watanabe.yu+github@gmail.com> | 2021-06-18 13:43:13 +0900 |
commit | e83580bfc6e74359ba242d5176d933ea1e723f89 (patch) | |
tree | d9bd3b6f599fcb51c890d7a7105435506af69c9b | |
parent | 29bff80b5c5a3146c9073d16d80b24d8584934a2 (diff) | |
download | systemd-e83580bfc6e74359ba242d5176d933ea1e723f89.tar.gz |
Update systemd-resolved.service.8 help
Text currently refers to `/etc/nsswitch.conf` where it should refer to `/etc/resolv.conf`.
This is in the context of defining a nameserver IP and search domains.
-rw-r--r-- | man/systemd-resolved.service.xml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 7d4d7bb16c..661e36b00b 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -242,7 +242,7 @@ control of the client library. <filename>nss-dns</filename> will first try to resolve names using search domains and even if those queries are routed to <filename>systemd-resolved</filename>, it will send them out over the network using the usual rules for multi-label name routing <footnote><para>For - example, if <filename>/etc/nsswitch.conf</filename> has <programlisting>nameserver 127.0.0.53 + example, if <filename>/etc/resolv.conf</filename> has <programlisting>nameserver 127.0.0.53 search foobar.com barbar.com </programlisting>and we look up <literal>localhost</literal>, <filename>nss-dns</filename> will send the following queries to <filename>systemd-resolved</filename> listening on 127.0.0.53:53: first |