diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 89ec5f8b19..27662456ea 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -1,4 +1,4 @@
-
+
@@ -71,6 +71,61 @@
systemd.network5
for more details.
+ systemd-resolved synthesizes DNS RRs for the following cases:
+
+
+ The local, configured hostname is resolved to
+ all locally configured IP addresses ordered by their scope, or
+ — if none are configured — the IPv4 address 127.0.0.2 (which
+ is on the local loopback) and the IPv6 address ::1 (which is the
+ local host).
+
+ The hostname localhost is
+ resolved to the IP addresses 127.0.0.1 and
+ ::1.
+
+ The hostname gateway is
+ resolved to all current default routing gateway addresses,
+ ordered by their metric. This assigns a stable hostname to the
+ current gateway, useful for referencing it independently of the
+ current network configuration state.
+
+
+ Lookup requests are routed to the available DNS servers
+ and LLMNR interfaces according to the following rules:
+
+
+ Lookups for the special hostname
+ localhost are never routed to the
+ network.
+
+ Single-label names are routed to all local
+ interfaces capable of IP multicasting, using the LLMNR
+ protocol. Lookups for IPv4 addresses are only sent via LLMNR on
+ IPv4, and lookups for IPv6 addresses are only sent via LLMNR on
+ IPv6. Lookups for the locally configured host name and the
+ gateway host name are never routed to
+ LLMNR.
+
+ Multi-label names are routed to all local
+ interfaces that have a DNS sever configured, plus the globally
+ configured DNS server if there is one. Address lookups from the
+ link-local addres range are never routed to
+ DNS.
+
+
+ If lookups are routed to multiple interfaces, the first
+ successful response is returned (thus effectively merging the
+ lookup zones on all matching interfaces). If the lookup failed on
+ all interfaces the last failing response is returned.
+
+ Routing of lookups may be influenced by configuring
+ per-interface domain names, see
+ systemd.network5
+ for details. Lookups for a hostname ending in one of the
+ per-interface domains are exclusively routed to the matching
+ interfaces.
+
Note that
/run/systemd/resolve/resolv.conf should not
be used directly, but only through a symlink from