chiark / gitweb /
man: update resolved man pages a bit
authorLennart Poettering <lennart@poettering.net>
Sun, 10 Aug 2014 21:40:18 +0000 (23:40 +0200)
committerLennart Poettering <lennart@poettering.net>
Mon, 11 Aug 2014 13:06:22 +0000 (15:06 +0200)
man/resolved.conf.xml
man/systemd-resolved.service.xml

index 6e0185b..c582368 100644 (file)
@@ -56,8 +56,8 @@
 
                 <para>When starting, systemd-resolved will read the
                 configuration file <filename>resolved.conf</filename>.
-                This configuration file controls local DNS name
-                resolving.</para>
+                This configuration file controls local DNS and LLMNR
+                name resolving.</para>
 
         </refsect1>
 
index 839f46a..dc0e3b6 100644 (file)
                 <title>Description</title>
 
                 <para><command>systemd-resolved</command> is a system
-                service that manages network name resolution. It does so by
-                generating <filename>/run/systemd/resolve/resolv.conf</filename>,
-                which may be symlinked from <filename>/etc/resolv.conf</filename>.
-                The contents is generated from the global settings in
+                service that manages network name resolution. It
+                implements a caching DNS stub resolver and an LLMNR
+                resolver and responder. It also generates
+                <filename>/run/systemd/resolve/resolv.conf</filename>
+                for compatibility which may be symlinked from
+                <filename>/etc/resolv.conf</filename>.  The DNS servers contacted
+                are determined from the global settings in
                 <citerefentry><refentrytitle>resolved.conf</refentrytitle><manvolnum>5</manvolnum></citerefentry>,
-                the per-link static settings in <filename>.network</filename> files,
-                and the per-link dynamic settings received over DHCP. See
+                the per-link static settings in
+                <filename>.network</filename> files, and the per-link
+                dynamic settings received over DHCP. See
                 <citerefentry><refentrytitle>systemd.network</refentrytitle><manvolnum>5</manvolnum></citerefentry>
                 for more details.</para>