diff options
-rw-r--r-- | man/systemd-resolved.service.xml | 15 |
1 files changed, 8 insertions, 7 deletions
diff --git a/man/systemd-resolved.service.xml b/man/systemd-resolved.service.xml index 9c7c482549..7d4d7bb16c 100644 --- a/man/systemd-resolved.service.xml +++ b/man/systemd-resolved.service.xml @@ -138,13 +138,14 @@ <listitem><para>Queries for the address records (A and AAAA) of single-label non-synthesized names are resolved via unicast DNS using search domains. For any interface which defines search domains, such - look-ups are routed to that interface, suffixed with each of the search domains defined on that - interface in turn. When global search domains are defined, such look-ups are routed to all interfaces, - suffixed by each of the global search domains in turn. Additionally, lookup of single-label names via - unicast DNS may be enabled with the <varname>ResolveUnicastSingleLabel=yes</varname> setting. The - details of which servers are queried and how the final reply is chosen are described below. Note that - this means that address queries for single-label names are never sent out to remote DNS servers by - default, and resoulution is only possible if search domains are defined.</para></listitem> + look-ups are routed to the servers defined for that interface, suffixed with each of those search + domains. When global search domains are defined, such look-ups are routed to the global servers. For + each search domain, queries are performed by suffixing the name with each of the search domains in + turn. Additionally, lookup of single-label names via unicast DNS may be enabled with the + <varname>ResolveUnicastSingleLabel=yes</varname> setting. The details of which servers are queried and + how the final reply is chosen are described below. Note that this means that address queries for + single-label names are never sent out to remote DNS servers by default, and resoulution is only + possible if search domains are defined.</para></listitem> <listitem><para>Multi-label names with the domain suffix <literal>.local</literal> are resolved using MulticastDNS on all local interfaces where MulticastDNS is enabled. As with LLMNR, IPv4 address lookups |