From e83580bfc6e74359ba242d5176d933ea1e723f89 Mon Sep 17 00:00:00 2001 From: plattrap Date: Fri, 18 Jun 2021 12:32:02 +1200 Subject: [PATCH] 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. --- man/systemd-resolved.service.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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. nss-dns will first try to resolve names using search domains and even if those queries are routed to systemd-resolved, it will send them out over the network using the usual rules for multi-label name routing For - example, if /etc/nsswitch.conf has nameserver 127.0.0.53 + example, if /etc/resolv.conf has nameserver 127.0.0.53 search foobar.com barbar.com and we look up localhost, nss-dns will send the following queries to systemd-resolved listening on 127.0.0.53:53: first -- 2.25.1