NAME<\/a> systemd-resolved.service, systemd-resolved \u2212 Network Name Resolution manager<\/p>\n systemd\u2212resolved.service<\/p>\n \/usr\/lib\/systemd\/systemd\u2212resolved<\/p>\n systemd\u2212resolved<\/b> 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 and MulticastDNS resolver and responder. Local applications may submit network name resolution requests via three interfaces:<\/p>\n \u2022 The native, fully\u2212featured API systemd\u2212resolved<\/b> exposes on the bus, see org.freedesktop.resolve1<\/b>(5) and org.freedesktop.LogControl1<\/b>(5) for details. Usage of this API is generally recommended to clients as it is asynchronous and fully featured (for example, properly returns DNSSEC validation status and interface scope for addresses as necessary for supporting link\u2212local networking).<\/p>\n \u2022 The glibc getaddrinfo<\/b>(3) API as defined by RFC3493<\/font><\/b> [1]<\/font><\/small> and its related resolver functions, including gethostbyname<\/b>(3). This API is widely supported, including beyond the Linux platform. In its current form it does not expose DNSSEC validation status information however, and is synchronous only. This API is backed by the glibc Name Service Switch (nss<\/b>(5)). Usage of the glibc NSS module nss-resolve<\/b>(8) is required in order to allow glibc’s NSS resolver functions to resolve hostnames via systemd\u2212resolved<\/b>.<\/font><\/p>\n \u2022 Additionally, systemd\u2212resolved<\/b> provides a local DNS stub listener on IP address 127.0.0.53 on the local loopback interface. Programs issuing DNS requests directly, bypassing any local API may be directed to this stub, in order to connect them to systemd\u2212resolved<\/b>. Note however that it is strongly recommended that local programs use the glibc NSS or bus APIs instead (as described above), as various network resolution concepts (such as link\u2212local addressing, or LLMNR Unicode domains) cannot be mapped to the unicast DNS protocol.<\/font><\/p>\n The DNS servers contacted are determined from the global settings in \/etc\/systemd\/resolved.conf, the per\u2212link static settings in \/etc\/systemd\/network\/*.network files (in case systemd-networkd.service<\/b>(8) is used), the per\u2212link dynamic settings received over DHCP, information provided via resolvectl<\/b>(1), and any DNS server information made available by other system services. See resolved.conf<\/b>(5) and systemd.network<\/b>(5) for details about systemd’s own configuration files for DNS servers. To improve compatibility, \/etc\/resolv.conf is read in order to discover configured system DNS servers, but only if it is not a symlink to \/run\/systemd\/resolve\/stub\u2212resolv.conf, \/usr\/lib\/systemd\/resolv.conf or \/run\/systemd\/resolve\/resolv.conf (see below).<\/font><\/p>\n systemd\u2212resolved<\/b> synthetizes DNS resource records (RRs) for the following cases:<\/font><\/p>\n \u2022 The local, configured hostname is resolved to all locally configured IP addresses ordered by their scope, or \u2014 if none are configured \u2014 the IPv4 address 127.0.0.2 (which is on the local loopback interface) and the IPv6 address ::1 (which is the local host).<\/font><\/p>\n \u2022 The hostnames “localhost” and “localhost.localdomain” as well as any hostname ending in “.localhost” or “.localhost.localdomain” are resolved to the IP addresses 127.0.0.1 and ::1.<\/font><\/p>\n \u2022 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.<\/font><\/p>\n \u2022 The mappings defined in \/etc\/hosts are resolved to their configured addresses and back, but they will not affect lookups for non\u2212address types (like MX). Support for \/etc\/hosts may be disabled with ReadEtcHosts=no<\/i>, see resolved.conf<\/b>(5).<\/font><\/p>\n Lookup requests are routed to the available DNS servers, LLMNR, and MulticastDNS interfaces according to the following rules:<\/font><\/p>\n \u2022 Names for which synthetic records are generated (the local hostname, “localhost” and “localdomain”, local gateway, as listed in the previous section) and addresses configured in \/etc\/hosts are never routed to the network and a reply is sent immediately.<\/font><\/p>\n \u2022 Single\u2212label names are resolved using LLMNR on all local interfaces where LLMNR is enabled. Lookups for IPv4 addresses are only sent via LLMNR on IPv4, and lookups for IPv6 addresses are only sent via LLMNR on IPv6. Note that lookups for single\u2212label synthetized names are not routed to LLMNR, MulticastDNS or unicast DNS.<\/font><\/p>\n \u2022 Queries for the address records (A and AAAA) of single\u2212label non\u2212synthetized names are resolved via unicast DNS using search domains. For any interface which defines search domains, such look\u2212ups 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\u2212ups are routed to all interfaces, suffixed by each of the global search domains in turn. Additionally, lookup of single\u2212label names via unicast DNS may be enabled with the ResolveUnicastSingleLabel=yes<\/i> 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\u2212label names are never sent out to remote DNS servers by default, and resoulution is only possible if search domains are defined.<\/font><\/p>\n \u2022 Multi\u2212label names with the domain suffix “.local” are resolved using MulticastDNS on all local interfaces where MulticastDNS is enabled. As with LLMNR, IPv4 address lookups are sent via IPv4 and IPv6 address lookups are sent via IPv6.<\/font><\/p>\n \u2022 Queries for multi\u2212label names are routed via unicast DNS on local interfaces that have a DNS server configured, plus the globally configured DNS servers if there are any. Which interfaces are used is determined by the routing logic based on search and route\u2212only domains, described below. 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\u2212specific DNS server, explicit search or routing domains need to be configured to make lookups work within this DNS domain. Note that these days, it’s generally recommended to avoid defining “.local” in a DNS server, as<\/font> RFC6762<\/font><\/b> [2]<\/font><\/small> reserves this domain for exclusive MulticastDNS use.<\/font><\/p>\n \u2022 Address lookups (reverse lookups) are routed similarly to multi\u2212label names, with the exception that addresses from the link\u2212local address range are never routed to unicast DNS and are only resolved using LLMNR and MulticastDNS (when enabled).<\/font><\/p>\n 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.<\/font><\/p>\n Routing of lookups is determined by the per\u2212interface routing domains (search and route\u2212only) and global search domains. See systemd.network<\/b>(5) and resolvectl<\/b>(1) for a description how those settings are set dynamically and the discussion of Domains=<\/i> in resolved.conf<\/b>(5) for a description of globally configured DNS settings.<\/font><\/p>\n The following query routing logic applies for unicast DNS traffic:<\/font><\/p>\n \u2022 If a name to look up matches (that is: is equal to or has as suffix) any of the configured routing domains (search or route\u2212only) of any link, or the globally configured DNS settings, “best matching” routing domain is determined: the matching one with the most labels. The query is then sent to all DNS servers of any links or the globally configured DNS servers associated with this “best matching” routing domain. (Note that more than one link might have this same “best matching” routing domain configured, in which case the query is sent to all of them in parallel).<\/font><\/p>\n In case of single\u2212label names, when search domains are defined, the same logic applies, except that the name is first suffixed by each of the search domains in turn. Note that this search logic doesn’t apply to any names with at least one dot. Also see the discussion about compatiblity with the traditional glibc resolver below.<\/font><\/p>\n \u2022 If a query does not match any configured routing domain (either per\u2212link or global), it is sent to all DNS servers that are configured on links with the DefaultRoute=<\/i> option set, as well as the globally configured DNS server.<\/font><\/p>\n \u2022 If there is no link configured as DefaultRoute=<\/i> and no global DNS server configured, one of the compiled\u2212in fallback DNS servers is used.<\/font><\/p>\n \u2022 Otherwise the unicast DNS query fails, as no suitable DNS servers can be determined.<\/font><\/p>\n The DefaultRoute=<\/i> option is a boolean setting configurable with resolvectl<\/b> or in .network files. If not set, it is implicitly determined based on the configured DNS domains for a link: if there’s a route\u2212only domain other than “~.”, it defaults to false, otherwise to true.<\/font><\/p>\n Effectively this means: in order to support single\u2212label non\u2212synthetized names, define appropriate search domains. In order to preferably route all DNS queries not explicitly matched by routing domain configuration to a specific link, configure a “~.” route\u2212only domain on it. This will ensure that other links will not be considered for these queries (unless they too carry such a routing domain). In order to route all such DNS queries to a specific link only if no other link is preferred, set the DefaultRoute=<\/i> option for the link to true and do not configure a “~.” route\u2212only domain on it. Finally, in order to ensure that a specific link never receives any DNS traffic not matching any of its configured routing domains, set the DefaultRoute=<\/i> option for it to false.<\/font><\/p>\n See the<\/font> resolved D\u2212Bus API Documentation<\/font><\/b> [3]<\/font><\/small> for information about the APIs systemd\u2212resolved provides.<\/font><\/p>\n This section provides a short summary of differences in the stub resolver implemented by nss-resolve<\/b>(8) together with systemd\u2212resolved<\/b> and the tranditional stub resolver implemented in nss-dns<\/b>(8).<\/font><\/p>\n \u2022 Some names are always resolved internally (see Synthetic Records above). Traditionally they would be resolved by nss\u2212files, and only if provided in \/etc\/hosts.<\/font><\/p>\n \u2022 Single\u2212label names are not resolved for A and AAAA records using unicast DNS (unless overriden with ResolveUnicastSingleLabel=<\/i>, see resolved.conf<\/b>(5)). This is similar to the no\u2212tld\u2212query<\/b> option being set in resolv.conf<\/b>(5).<\/font><\/p>\n \u2022 Search domains are not used for suffixing<\/i> of multi\u2212label names. (Search domains are nevertheless used for lookup routing<\/i>, for names that were originally specified as single\u2212label or multi\u2212label.) Any name with at least one dot is always interpreted as a FQDN. nss\u2212dns would resolve names both as relative (using search domains) and absolute FQDN names. Some names would be resolved as relative first, and after that query has failed, as absolute, while other names would be resolved in opposite order. The ndots<\/i> option in \/etc\/resolv.conf was used to control how many dots the name needs to have to be resolved as relative first. This stub resolver does not implement this at all: multi\u2212label names are only resolved as FQDNs. (There are currently more than 1500 top\u2212level domain names defined, and new ones are added regularly, often using “attractive” names that are also likely to be used locally. Not looking up multi\u2212label names in this fashion avoids fragility in both directions: a valid global name could be obscured by a local name, and resolution of a relative local name could suddenly break when a new top\u2212level domain is created, or when a new subdomain of a top\u2212level domain in registered. Resolving any given name as either relative or absolute avoids this ambiguity.)<\/font><\/p>\n \u2022 This resolver has a notion of the special “.local” domain used for MulticastDNS, and will not route queries with that suffix to unicast DNS servers unless explicitly configured, see above. Also, reverse lookups for link\u2212local addresses are not sent to unicast DNS servers.<\/font><\/p>\n \u2022 This resolver reads and caches \/etc\/hosts internally. (In other words, nss\u2212resolve replaces nss\u2212files in addition to nss\u2212dns). Entries in \/etc\/hosts have highest priority.<\/font><\/p>\n \u2022 This resolver also implements LLMNR and MulticastDNS in addition to the classic unicast DNS protocol, and will resolve single\u2212label names using LLMNR (when enabled) and names ending in “.local” using MulticastDNS (when enabled).<\/font><\/p>\n \u2022 Environment variables $LOCALDOMAIN<\/i> and $RES_OPTIONS<\/i> described in resolv.conf<\/b>(5) are not supported currently.<\/font><\/p>\n Four modes of handling \/etc\/resolv.conf (see resolv.conf<\/b>(5)) are supported:<\/font><\/p>\n \u2022 systemd\u2212resolved<\/b> maintains the \/run\/systemd\/resolve\/stub\u2212resolv.conf file for compatibility with traditional Linux programs. This file may be symlinked from \/etc\/resolv.conf. This file lists the 127.0.0.53 DNS stub (see above) as the only DNS server. It also contains a list of search domains that are in use by systemd\u2212resolved. The list of search domains is always kept up\u2212to\u2212date. Note that \/run\/systemd\/resolve\/stub\u2212resolv.conf should not be used directly by applications, but only through a symlink from \/etc\/resolv.conf. This file may be symlinked from \/etc\/resolv.conf in order to connect all local clients that bypass local DNS APIs to systemd\u2212resolved<\/b> with correct search domains settings. This mode of operation is recommended.<\/font><\/p>\n \u2022 A static file \/usr\/lib\/systemd\/resolv.conf is provided that lists the 127.0.0.53 DNS stub (see above) as only DNS server. This file may be symlinked from \/etc\/resolv.conf in order to connect all local clients that bypass local DNS APIs to systemd\u2212resolved<\/b>. This file does not contain any search domains.<\/font><\/p>\n \u2022 systemd\u2212resolved<\/b> maintains the \/run\/systemd\/resolve\/resolv.conf file for compatibility with traditional Linux programs. This file may be symlinked from \/etc\/resolv.conf and is always kept up\u2212to\u2212date, containing information about all known DNS servers. Note the file format’s limitations: it does not know a concept of per\u2212interface DNS servers and hence only contains system\u2212wide DNS server definitions. Note that \/run\/systemd\/resolve\/resolv.conf should not be used directly by applications, but only through a symlink from \/etc\/resolv.conf. If this mode of operation is used local clients that bypass any local DNS API will also bypass systemd\u2212resolved<\/b> and will talk directly to the known DNS servers.<\/font><\/p>\n \u2022 Alternatively, \/etc\/resolv.conf may be managed by other packages, in which case systemd\u2212resolved<\/b> will read it for DNS configuration data. In this mode of operation systemd\u2212resolved<\/b> is consumer rather than provider of this configuration file.<\/font><\/p>\n Note that the selected mode of operation for this file is detected fully automatically, depending on whether \/etc\/resolv.conf is a symlink to \/run\/systemd\/resolve\/resolv.conf or lists 127.0.0.53 as DNS server.<\/font><\/p>\n SIGUSR1<\/b><\/font><\/p>\n Upon reception of the SIGUSR1<\/b> process signal systemd\u2212resolved<\/b> will dump the contents of all DNS resource record caches it maintains, as well as all feature level information it learnt about configured DNS servers into the system logs.<\/font><\/p>\n SIGUSR2<\/b><\/font><\/p>\n Upon reception of the SIGUSR2<\/b> process signal systemd\u2212resolved<\/b> will flush all caches it maintains. Note that it should normally not be necessary to request this explicitly \u2013 except for debugging purposes \u2013 as systemd\u2212resolved<\/b> flushes the caches automatically anyway any time the host’s network configuration changes. Sending this signal to systemd\u2212resolved<\/b> is equivalent to the resolvectl flush\u2212caches<\/b> command, however the latter is recommended since it operates in a synchronous way.<\/font><\/p>\n SIGRTMIN+1<\/b><\/font><\/p>\n Upon reception of the SIGRTMIN+1<\/b> process signal systemd\u2212resolved<\/b> will forget everything it learnt about the configured DNS servers. Specifically any information about server feature support is flushed out, and the server feature probing logic is restarted on the next request, starting with the most fully featured level. Note that it should normally not be necessary to request this explicitly \u2013 except for debugging purposes \u2013 as systemd\u2212resolved<\/b> automatically forgets learnt information any time the DNS server configuration changes. Sending this signal to systemd\u2212resolved<\/b> is equivalent to the resolvectl reset\u2212server\u2212features<\/b> command, however the latter is recommended since it operates in a synchronous way.<\/font><\/p>\n systemd<\/b>(1), resolved.conf<\/b>(5), dnssec-trust-anchors.d<\/b>(5), nss-resolve<\/b>(8), resolvectl<\/b>(1), resolv.conf<\/b>(5), hosts<\/b>(5), systemd.network<\/b>(5), systemd-networkd.service<\/b>(8)<\/font><\/p>\n 1.<\/font><\/p>\n<\/td>\n RFC3493<\/font><\/p>\n<\/td>\n https:\/\/tools.ietf.org\/html\/rfc3493<\/font><\/p>\n 2.<\/font><\/p>\n<\/td>\n RFC6762<\/font><\/p>\n<\/td>\n https:\/\/tools.ietf.org\/html\/rfc6762<\/font><\/p>\n 3.<\/font><\/p>\n<\/td>\n resolved D-Bus API Documentation<\/font><\/p>\n<\/td>\n https:\/\/www.freedesktop.org\/wiki\/Software\/systemd\/resolved<\/font><\/p>\n systemd-resolved.service, systemd-resolved \u2212 Network Name Resolution manager <\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[5,52,4,861],"class_list":["post-3758","post","type-post","status-publish","format-standard","hentry","category-8-administracion-del-sistema","tag-5","tag-administracion","tag-man8","tag-systemd-resolved"],"gutentor_comment":0,"_links":{"self":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3758","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/comments?post=3758"}],"version-history":[{"count":0,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/posts\/3758\/revisions"}],"wp:attachment":[{"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/media?parent=3758"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/categories?post=3758"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/lode.uno\/linux-man\/wp-json\/wp\/v2\/tags?post=3758"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
SYNOPSIS<\/a>
DESCRIPTION<\/a>
SYNTHETIC RECORDS<\/a>
PROTOCOLS AND ROUTING<\/a>
COMPATIBILITY WITH THE TRADITIONAL GLIBC STUB RESOLVER<\/a>
\/ETC\/RESOLV.CONF<\/a>
SIGNALS<\/a>
SEE ALSO<\/a>
NOTES<\/a> <\/p>\n
\nNAME <\/a> <\/h2>\n
SYNOPSIS <\/a> <\/h2>\n
DESCRIPTION <\/a> <\/h2>\n
SYNTHETIC RECORDS <\/a> <\/h2>\n
PROTOCOLS AND ROUTING <\/a> <\/h2>\n
COMPATIBILITY WITH THE TRADITIONAL GLIBC STUB RESOLVER <\/a> <\/h2>\n
\/ETC\/RESOLV.CONF <\/a> <\/h2>\n
SIGNALS <\/a> <\/h2>\n
SEE ALSO <\/a> <\/h2>\n
NOTES <\/a> <\/h2>\n
\n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n \n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n \n
\n <\/td>\n \n <\/td>\n \n <\/td>\n<\/tr>\n<\/table>\n
\n","protected":false},"excerpt":{"rendered":"