man: try to clarify that nss-mymachines does not provide name resolution outside...

Fixes: #18229
(cherry picked from commit 74c88a25203e7db293ca7a1c31b789e6558129fd)

diff --git a/man/nss-mymachines.xml b/man/nss-mymachines.xml
index b2785df410c19992e840fd7e7eca5fe50864a2fc..7ca9a581323422609dc1ddcbab8b01bdcb9d6826 100644 (file)
--- a/man/nss-mymachines.xml
+++ b/man/nss-mymachines.xml
@@ -39,6 +39,15 @@
     Note that the name that is resolved is the one registered with <command>systemd-machined</command>, which
     may be different than the hostname configured inside of the container.</para>
 
+    <para>Note that this NSS module only makes available names of the containers running immediately below
+    the current system context. It does not provide host name resolution for containers running side-by-side
+    with the invoking system context, or containers further up or down the container hierarchy. Or in other
+    words, on the host system it provides host name resolution for the containers running immediately below
+    the host environment. When used inside a container environment however, it will not be able to provide
+    name resolution for containers running on the host (as those are siblings and not children of the current
+    container environment), but instead only for nested containers running immediately below its own
+    container environment.</para>
+
     <para>To activate the NSS module, add <literal>mymachines</literal> to the line starting with
     <literal>hosts:</literal> in <filename>/etc/nsswitch.conf</filename>.</para>