Stubby is an application that acts as a local DNS Privacy stub resolver (using DNS-over-TLS). Stubby encrypts DNS queries sent from a client machine (desktop or laptop) to a DNS Privacy resolver increasing end user privacy.
Install the package.
To configure stubby, perform the following steps:
Upon installation, Stubby has some default resolvers. They can be found and edited in
/etc/stubby/stubby.yml. You can use the defaults, uncomment one of prewritten resolvers or find another resolver from this list.
Example of a valid resolver configuration:
upstream_recursive_servers: # The Surfnet/Sinodun servers - address_data: 220.127.116.11 tls_auth_name: "dnsovertls.sinodun.com" tls_pubkey_pinset: - digest: "sha256" value: 62lKu9HsDVbyiPenApnc4sfmSYTHOVfFgL3pyB+cBL4= # The Cloudflare server - address_data: 18.104.22.168 tls_port: 853 tls_auth_name: "cloudflare-dns.com"
After selecting a resolver, modify the resolv.conf file and replace the current set of resolver addresses with address for localhost:
Other programs may overwrite this setting; see resolv.conf#Preserve DNS settings for details.
Start systemd service
Finally, start and enable the
Tips and tricks
Local DNS cache configuration
Stubby does not have a built-in DNS cache, therefore every single query is transmitted and resolved, which can slow down connections. Setting up a dns cache requires installing and configuring a seperate dns cacher.
In order to forward to a local DNS cache, Stubby should listen on a port different from the default
53, since the DNS cache itself needs to listen on
53 and query Stubby on a different port. Port number
53000 is used as an example in this section. In this example, the port number is larger than 1024 so stubby is not required to be run by root.
Edit the value of
/etc/stubby/stubby.yml as follows:
listen_addresses: - 127.0.0.1@53000 - 0::1@53000
Configure dnsmasq as a local DNS cache. The basic configuration to work with Stubby is the following:
no-resolv proxy-dnssec server=127.0.0.1#53000 listen-address=127.0.0.1
dnsmasq.service to apply the changes.
Other DNS cachers
For more dns cachers, see DNSCrypt#Local DNS cache configuration. The configurations should be similar if not identical.