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

diff --git a/man/nss-myhostname.xml b/man/nss-myhostname.xml
index 4a33149a73acfbbeb77a3cf33fcdc1a59dfffed5..f9d0ff43f4399463e07f31b2211c67711c4dd08b 100644 (file)
--- 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 97c3768100bacac9ef1fc51e3ff67f59e2e7a785..4f9e1f9c5a58f27e2702216df5bb0f93ec3ec17f 100644 (file)
--- 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>