resolvectl, resolvconf - Resolve domain names, IPV4 and IPv6 addresses, DNS resource records, and services; introspect and reconfigure the DNS resolver
may be used to resolve domain names, IPv4 and IPv6 addresses, DNS resource records and services with the
resolver service. By default, the specified list of parameters will be resolved as hostnames, retrieving their IPv4 and IPv6 addresses. If the parameters specified are formatted as IPv4 or IPv6 operation the reverse operation is done, and a hostname is retrieved for the specified addresses.
The program's output contains information about the protocol used for the look-up and on which network interface the data was discovered. It also contains information on whether the information could be authenticated. All data for which local DNSSEC validation succeeds is considered authenticated. Moreover all data originating from local, trusted sources is also reported authenticated, including resolution of the local host name, the
hostname or all data from
Resolve domain names, IPv4 and IPv6 addresses.
service [[NAME] TYPE] DOMAIN
services, depending on the specified list of parameters. If three parameters are passed the first is assumed to be the DNS-SD service name, the second the SRV service type, and the third the domain to search in. In this case a full DNS-SD style SRV and TXT lookup is executed. If only two parameters are specified, the first is assumed to be the SRV service type, and the second the domain to look in. In this case no TXT RR is requested. Finally, if only one parameter is specified, it is assumed to be a domain name, that is already prefixed with an SRV type, and an SRV lookup is done (no TXT).
Query PGP keys stored as
resource records. Specified e-mail addresses are converted to the corresponding DNS domain name, and any OPENPGPKEY keys are printed.
tlsa [FAMILY] DOMAIN[:PORT]...
Query TLS public keys stored as
resource records. A query will be performed for each of the specified names prefixed with the port and family ("_port._family.domain"). The port number may be specified after a colon (":"), otherwise
will be used by default. The family may be specified as the first argument, otherwise
will be used.
Shows the global and per-link DNS settings currently in effect. If no command is specified, this is the implied default.
Shows general resolver statistics, including information whether DNSSEC is enabled and available, as well as resolution and validation statistics.
Resets the statistics counters shown in
to zero. This operation requires root privileges.
Flushes all DNS resource record caches the service maintains locally. This is mostly equivalent to sending the
Flushes all feature level information the resolver learnt about specific servers, and ensures that the server feature probing logic is started from the beginning with the next look-up request. This is mostly equivalent to sending the
dns [LINK [SERVER...]], domain [LINK [DOMAIN...]], default-route [LINK [BOOL...]], llmnr [LINK [MODE]], mdns [LINK [MODE]], dnssec [LINK [MODE]], dnsovertls [LINK [MODE]], nta [LINK [DOMAIN...]]
Get/set per-interface DNS configuration. These commands may be used to configure various DNS settings for network interfaces. These commands may be used to inform
about per-interface DNS configuration determined through external means. The
command expects IPv4 or IPv6 address specifications of DNS servers to use. Each address can optionally take a port number separated with
":", a network interface name or index separated with
"%", and a Server Name Indication (SNI) separated with
"#". When IPv6 address is specified with a port number, then the address must be in the square brackets. That is, the acceptable full formats are
for IPv4 and
for IPv6. The
command expects valid DNS domains, possibly prefixed with
"~", and configures a per-interface search or route-only domain. The
command expects a boolean parameter, and configures whether the link may be used as default route for DNS lookups, i.e. if it is suitable for lookups on domains no other link explicitly is configured for. The
commands may be used to configure the per-interface LLMNR, MulticastDNS, DNSSEC and DNSOverTLS settings. Finally,
command may be used to configure additional per-interface DNSSEC NTA domains.
can take a single empty string argument to clear their respective value lists.
For details about these settings, their possible values and their effect, see the corresponding settings in
Revert the per-interface DNS configuration. If the DNS configuration is reverted all per-interface DNS setting are reset to their defaults, undoing all effects of
nta. Note that when a network interface disappears all configuration is lost automatically, an explicit reverting is not necessary in that case.
If no argument is given, print the current log level of the manager. If an optional argument
is provided, then the command changes the current log level of the manager to
(accepts the same values as
By default, when resolving a hostname, both IPv4 and IPv6 addresses are acquired. By specifying
only IPv4 addresses are requested, by specifying
only IPv6 addresses are requested.
-i INTERFACE, --interface=INTERFACE
Specifies the network interface to execute the query on. This may either be specified as numeric interface index or as network interface string (e.g.
"en0"). Note that this option has no effect if system-wide DNS configuration (as configured in
/etc/systemd/resolve.conf) in place of per-link configuration is used.
-p PROTOCOL, --protocol=PROTOCOL
Specifies the network protocol for the query. May be one of
(i.e. classic unicast DNS),
(m[blue]Link-Local Multicast Name Resolutionm),
(LLMNR via the indicated underlying IP protocols),
(MDNS via the indicated underlying IP protocols). By default the lookup is done via all protocols suitable for the lookup. If used, limits the set of protocols that may be used. Use this option multiple times to enable resolving via multiple protocols at the same time. The setting
is identical to specifying this switch once with
and once via
"llmnr-ipv6". Note that this option does not force the service to resolve the operation with the specified protocol, as that might require a suitable network interface and configuration. The special value
may be used to list known values.
-t TYPE, --type=TYPE, -c CLASS, --class=CLASS
Specifies the DNS resource record type (e.g. A, AAAA, MX, ...) and class (e.g. IN, ANY, ...) to look up. If these options are used a DNS resource record set matching the specified class and type is requested. The class defaults to IN if only a type is specified. The special value
may be used to list known values.
Takes a boolean parameter. If true (the default), when doing a service lookup with
the hostnames contained in the SRV resource records are resolved as well.
Takes a boolean parameter. If true (the default), when doing a DNS-SD service lookup with
the TXT service metadata record is resolved as well.
Takes a boolean parameter. If true (the default), DNS CNAME or DNAME redirections are followed. Otherwise, if a CNAME or DNAME record is encountered while resolving, an error is returned.
Takes a boolean parameter. If true (the default), any specified single-label hostnames will be searched in the domains configured in the search domain list, if it is non-empty. Otherwise, the search domain logic is disabled.
Dump the answer as binary data. If there is no argument or if the argument is
"payload", the payload of the packet is exported. If the argument is
"packet", the whole packet is dumped in wire format, prefixed by length specified as a little-endian 64-bit number. This format allows multiple packets to be dumped and unambiguously parsed.
Takes a boolean parameter. If true (the default), column headers and meta information about the query response are shown. Otherwise, this output is suppressed.
Print a short help text and exit.
Print a short version string and exit.
Do not pipe output into a pager.
COMPATIBILITY WITH RESOLVCONF(8)
is a multi-call binary. When invoked as
(generally achieved by means of a symbolic link of this name to the
binary) it is run in a limited
compatibility mode. It accepts mostly the same arguments and pushes all data into
systemd-resolved.service(8), similar to how
commands operate. Note that
is the only supported backend, which is different from other implementations of this command.
will only be updated with servers added with this command when
is a symlink to
/run/systemd/resolve/resolv.conf, and not a static file. See the discussion of
Not all operations supported by other implementations are supported natively. Specifically:
Registers per-interface DNS configuration data with
systemd-resolved. Expects a network interface name as only command line argument. Reads
resolv.conf(5)-compatible DNS configuration data from its standard input. Relevant fields are
"domain"/"search". This command is mostly identical to invoking
with a combination of
Unregisters per-interface DNS configuration data with
systemd-resolved. This command is mostly identical to invoking
will not complain about missing network interfaces and will silently execute no operation in that case.
This switch for "exclusive" operation is supported only partially. It is mapped to an additional configured search domain of
--- i.e. ensures that DNS traffic is preferably routed to the DNS servers on this interface, unless there are other, more specific domains configured on other interfaces.
These switches are not supported and are silently ignored.
-u, -I, -i, -l, -R, -r, -v, -V, --enable-updates, --disable-updates, --are-updates-enabled
These switches are not supported and the command will fail if used.
for details on those command line options.
Example 1. Retrieve the addresses of the "www.0pointer.net" domain
$ resolvectl query www.0pointer.net
-- Information acquired via protocol DNS in 611.6ms.
-- Data is authenticated: no
Example 2. Retrieve the domain of the "22.214.171.124" IP address
$ resolvectl query 126.96.36.199
-- Information acquired via protocol DNS in 1.2997s.
-- Data is authenticated: no
Example 3. Retrieve the MX record of the "yahoo.com" domain
$ resolvectl --legend=no -t MX query yahoo.com
yahoo.com. IN MX 1 mta7.am0.yahoodns.net
yahoo.com. IN MX 1 mta6.am0.yahoodns.net
yahoo.com. IN MX 1 mta5.am0.yahoodns.net
Example 4. Resolve an SRV service
$ resolvectl service _xmpp-server._tcp gmail.com
_xmpp-server._tcp/gmail.com: alt1.xmpp-server.l.google.com:5269 [priority=20, weight=0]
alt4.xmpp-server.l.google.com:5269 [priority=20, weight=0]
Example 5. Retrieve a PGP key
$ resolvectl openpgp firstname.lastname@example.org
d08ee310438ca124a6149ea5cc21b6313b390dce485576eff96f8722._openpgpkey.fedoraproject.org. IN OPENPGPKEY
Example 6. Retrieve a TLS key ("tcp" and ":443" could be skipped)
$ resolvectl tlsa tcp fedoraproject.org:443
_443._tcp.fedoraproject.org IN TLSA 0 0 1 19400be5b7a31fb733917700789d2f0a2471c0c9d506c0e504c06c16d7cb17c0
-- Cert. usage: CA constraint
-- Selector: Full Certificate
-- Matching type: SHA-256
Link-Local Multicast Name Resolution