From: Florian Klink <flokli@flokli.de>
Date: Sat, 17 Jul 2021 17:49:42 +0000 (+0200)
Subject: man: document nss-{resolve,myhostname} resolving in the other direction, too
X-Git-Tag: v250-rc1~929^2
X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=refs%2Fpull%2F20103%2Fhead;p=thirdparty%2Fsystemd.git

man: document nss-{resolve,myhostname} resolving in the other direction, too
---

diff --git a/man/nss-myhostname.xml b/man/nss-myhostname.xml
index 4a33149a73a..f9d0ff43f43 100644
--- a/man/nss-myhostname.xml
+++ b/man/nss-myhostname.xml
@@ -77,7 +77,12 @@
     This resolves well-known hostnames like <literal>localhost</literal>
     and the machine hostnames locally. It is consistent with the behaviour
     of <command>nss-resolve</command>, and still allows overriding via
-    <filename>/etc/hosts</filename>.
+    <filename>/etc/hosts</filename>.</para>
+
+    <para>Please keep in mind that <command>nss-myhostname</command> (and <command>nss-resolve</command>) also resolve
+    in the other direction — from locally attached IP adresses to
+    hostnames. If you rely on that lookup being provided by DNS, you might
+    want to order things differently.
     </para>
   </refsect1>
 
diff --git a/man/nss-resolve.xml b/man/nss-resolve.xml
index 97c3768100b..4f9e1f9c5a5 100644
--- a/man/nss-resolve.xml
+++ b/man/nss-resolve.xml
@@ -52,6 +52,12 @@
     it is still recommended (see examples below) to keep <command>nss-myhostname</command> configured in
     <filename>/etc/nsswitch.conf</filename>, to keep those names resolveable if
     <command>systemd-resolved</command> is not running.</para>
+
+    <para>Please keep in mind that <command>nss-myhostname</command> (and <command>nss-resolve</command>) also resolve
+    in the other direction — from locally attached IP adresses to
+    hostnames. If you rely on that lookup being provided by DNS, you might
+    want to order things differently.
+    </para>
   </refsect1>
 
   <refsect1>