From: plattrap <plattrap@yahoo.com>
Date: Fri, 18 Jun 2021 00:32:02 +0000 (+1200)
Subject: Update systemd-resolved.service.8 help
X-Git-Tag: v249-rc2~43
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=e83580bfc6e74359ba242d5176d933ea1e723f89;p=thirdparty%2Fsystemd.git

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.
---

diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 7d4d7bb16cc..661e36b00b2 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