diff options
| author | Lennart Poettering <lennart@poettering.net> | 2021-10-28 10:53:55 +0200 |
|---|---|---|
| committer | Zbigniew Jędrzejewski-Szmek <zbyszek@in.waw.pl> | 2021-11-10 15:01:30 +0100 |
| commit | 65aca93f2c64155b029388a69a768c37f0614e93 (patch) | |
| tree | d416fd2e5892b5f6d836f3737f226382c249e21c | |
| parent | 37ade0494a2ca154b107b79766d45f242eacb1cf (diff) | |
| download | systemd-65aca93f2c64155b029388a69a768c37f0614e93.tar.gz | |
man: document how nss-resolve and systemd-resolved communicate
Fixes: #20925
(cherry picked from commit 1d697549887d68953058049fcd833fa93a74402a)
| -rw-r--r-- | man/nss-resolve.xml | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/man/nss-resolve.xml b/man/nss-resolve.xml index 4f9e1f9c5a..d8957dd346 100644 --- a/man/nss-resolve.xml +++ b/man/nss-resolve.xml @@ -58,6 +58,10 @@ hostnames. If you rely on that lookup being provided by DNS, you might want to order things differently. </para> + + <para>Communication between <command>nss-resolve</command> and + <filename>systemd-resolved.service</filename> takes place via the + <filename>/run/systemd/resolve/io.systemd.Resolve</filename> <constant>AF_UNIX</constant> socket.</para> </refsect1> <refsect1> |