diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml
index 9ca1133fed..91887861ee 100644
--- a/man/systemd-resolved.service.xml
+++ b/man/systemd-resolved.service.xml
@@ -46,8 +46,8 @@
Description
systemd-resolved is a system service that provides network name resolution to local
- applications. It implements a caching and validating DNS/DNSSEC stub resolver, as well as an LLMNR resolver and
- responder. Local applications may submit network name resolution requests via three interfaces:
+ applications. It implements a caching and validating DNS/DNSSEC stub resolver, as well as an LLMNR and MulticastDNS
+ resolver and responder. Local applications may submit network name resolution requests via three interfaces:
The native, fully-featured API systemd-resolved exposes on the bus. See the
@@ -77,8 +77,10 @@
The DNS servers contacted are determined from the global settings in
/etc/systemd/resolved.conf, the per-link static settings in
- /etc/systemd/network/*.network files, the per-link dynamic settings received over DHCP and any
- DNS server information made available by other system services. See
+ /etc/systemd/network/*.network files (in case
+ systemd-networkd.service8 is
+ used), the per-link dynamic settings received over DHCP and any DNS server information made available by other
+ system services. See
resolved.conf5 and
systemd.network5 for details
about systemd's own configuration files for DNS servers. To improve compatibility,
@@ -111,27 +113,31 @@
non-address types (like MX).
- Lookup requests are routed to the available DNS servers
- and LLMNR interfaces according to the following rules:
+ Lookup requests are routed to the available DNS servers, LLMNR and MulticastDNS interfaces according to the
+ following rules:
- Lookups for the special hostname
- localhost are never routed to the
- network. (A few other, special domains are handled the same way.)
+ Lookups for the special hostname localhost are never routed to the network. (A
+ few other, special domains are handled the same way.)
- 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.
+ 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 server configured, plus the globally
- configured DNS server if there is one. Address lookups from the
- link-local address range are never routed to
- DNS.
+ Multi-label names with the domain suffix .local are routed to all local
+ interfaces capable of IP multicasting, using the MulticastDNS protocol. As with LLMNR IPv4 address lookups are
+ sent via IPv4 and IPv6 address lookups are sent via IPv6.
+
+ Other multi-label names are routed to all local interfaces that have a DNS server configured,
+ plus the globally configured DNS server if there is one. Address lookups from the link-local address range are
+ never routed to DNS. Note that by default lookups for domains with the .local suffix are not
+ routed to DNS servers, unless the domain is specified explicitly as routing or search domain for the DNS server
+ and interface. This means that on networks where the .local domain is defined in a
+ site-specific DNS server, explicit search or routing domains need to be configured to make lookups within this
+ DNS domain work. Note that today it's generally recommended to avoid defining .local in a DNS
+ server, as RFC6762 reserves this domain for exclusive
+ MulticastDNS use.
If lookups are routed to multiple interfaces, the first