It is recommended to use the default configuration file provided which will use ‘Strict’ privacy mode and spread the DNS queries among several of the current DNS Privacy test servers. Note that this file contains both IPv4 and IPv6 addresses.
Note also that this file only enables a small subset of the available servers by default. Users can choose to use additional servers by uncommenting the relevant sections in the file. See DNS Privacy Test Servers for details of the available servers.
As announced over the last 6 months, the dnsovertls*.sinodun.com nameservers were decommissioned on 9th Septemter 2022. See this announcement.
Alternatively the configuration file location can be specified on the
command line using the
-C flag. Changes to the configuration file
require a restart of Stubby.
From release 0.1.3 of stubby (using the 1.2 release of getdns) the
configuration file format is a YAML like format, which contains detailed
comments of the options. See here for an
or keep reading for a short description. To be backwards compatible a
file using the YAML format must have a .yml or .yaml extension.
The previously used JSON like format used internally in
is still supported but only when the configuration file is specified via
the command line using the -C flag. This format is the same as the
output returned by
stubby -i. For example, this output can be used as
a configuration file directly, but a less verbose form is also accepted.
Essentially the options available are the same as the options that can
be set on a getdns
contextoptions is available here.
To aid with creating a custom configuration file, an example is given below. The config file below will configure Stubby in the following ways:
resolution_type: Work in stub mode only (not recursive mode) - required for Stubby operation.
dns_transport_list: Use TLS only as a transport (no fallback to UDP or TCP).
tls_authentication: Use Strict Privacy i.e. require a TLS connection and authentication of the upstream
tls_query_padding_blocksize: Use the EDNS0 padding option to pad DNS queries to hide their size
edns_client_subnet_private: Use EDNS0 Client Subnet privacy so the client subnet is not sent to authoritative servers
listen_address: have the Stubbby daemon listen on IPv4 and IPv6 on port 53 on the loopback address
idle_timeout: Use an EDNS0 Keepalive idle timeout of 10s unless overridden by the server. This keeps idle TLS connections open to avoid the overhead of opening a new connection for every query.
round_robin_upstreams: Round robin queries across all the configured upstream servers. Without this option Stubby will use each upstream server sequentially until it becomes unavailable and then move on to use the next.
upstream_recursive_servers: Use the NLnet labs test DNS Privacy Server for outgoing queries. In Strict Privacy mode, at least one of the following is required for each nameserver:
tls_auth_name: This is the authentication domain name that will be verified against the presented certificate.
tls_pubkey_pinset: The sha256 SPKI pinset for the server. This is also verified against the presented certificate.
resolution_type: GETDNS_RESOLUTION_STUB dns_transport_list: - GETDNS_TRANSPORT_TLS tls_authentication: GETDNS_AUTHENTICATION_REQUIRED tls_query_padding_blocksize: 256 edns_client_subnet_private : 1 idle_timeout: 10000 listen_addresses: - 127.0.0.1 - 0::1 round_robin_upstreams: 1 upstream_recursive_servers: - address_data: 184.108.40.206 tls_auth_name: "getdnsapi.net" tls_pubkey_pinset: digest: "sha256" value: foxZRnIh9gZpWnl+zEiKa0EJ2rdCGroMWm02gaxSc9Q=
Additional privacy servers can be specified by adding more entries to
upstream_recursive_servers list above (note a separate entry must
be made for the IPv4 and IPv6 addresses of a given server. More DNS
Privacy test servers are
A custom port can be specified by adding the
tls_port: attribute to
upstream_recursive_server in the config file.
A custom listen address port can be configured by using the <IP_address>@<port> syntax
To enable DNSSEC validation when using Stubby add the following option to the configuration file
A trust anchor is also required for DNSSEC validation.
getdns version 1.2 and later include support for automatic trust anchor management - which will automatically fetch a trust anchor if none is present on the system. See ‘Zero configuration DNSSEC’ (and below) for the specific details of key management for DNSSEC for this case. If using a version of getdns earlier than 1.2 then a trust anchor must be manually installed and managed on the system. We recommend using unbound-anchor.
When the system-level user does have a home directory, stubby will store the for Zero configuration DNSSEC dynamically acquired root trust anchor in a subdirectory called “.getdns” of that home directory (or in “%AppData%\getdns” on Windows). If the system-level user does not have a home directory or the home directory is not writeable or readable, stubby will fallback to the current working directory.
This can be overruled by supplying a “
appdata_dir” in the
configuration file. When a “
appdata_dir” was specified, that directory
will be used for storing data related to Zero configuration DNSSEC
immediately, without the other paths being tried. It is recommended for
systemd setups using the provided systemd.service file(s) to have a
appdata_dir” directive set to “
/var/cache/stubby” in the stubby.yml
Note that using DNSSEC can add a small performance overhead because it increases the number of queries required to resolve a DNS request.
Some users may want to have a configuration for Stubby that will always use the resolver from the system configuration (most likely but not always on the local network), but with encryption used where possible. This is an Opportunistic mode which does not authenticate the DoT server. To configure Stubby in this mode:
Set the transport list and authentication parameter in the configuration to:
dns_transport_list: - GETDNS_TRANSPORT_TLS - GETDNS_TRANSPORT_UDP - GETDNS_TRANSPORT_TCP tls_authentication: GETDNS_AUTHENTICATION_NONE
Remove (or comment out) all the upstream_resolvers. This will cause Stubby to fallback to using the system resolvers only.
Note: a future version of Stubby will most likely support a mixed mode of system resolvers and configured resolvers.
In the 0.1.2 release of stubby there is runtime logging, which can be turned on by using the ‘-l’ flag.
In the 0.1.3 release the logging level is be controlled by specifying a logging level via the ‘-v’ flag. See stubby help (‘stubby -h’) for more details.