dnss is a daemon for using DNS over HTTPS.

It can act as a proxy, receiving DNS requests and resolving them using DNS-over-HTTPs (DoH). This can be useful to improve DNS security and privacy on laptops and small/home networks.

It can also act as a DoH server, in case you want end to end control.

• Supports the DNS Queries over HTTPS (DoH) standard (RFC 8484).
• Local cache (optional).
• HTTP(s) proxy support, autodetected from the environment.
• Monitoring HTTP server, with exported variables and tracing to help debugging.
• Separate resolution for specific domains, useful for home networks with local DNS servers.

The dnss package installs the daemon configured in proxy mode and ready to use, using Google's public resolvers (and easily changed via configuration).

sudo apt install dnss

To clone the repository and build the binary:

git clone https://blitiri.com.ar/repos/dnss
cd dnss
go build

And if you want to configure the daemon to be automatically run by systemd:

# Copy the binary to a system-wide location.
sudo cp dnss /usr/local/bin/
# Set it up in systemd.
sudo cp etc/systemd/dns-to-https/*  /etc/systemd/system/
sudo systemctl dnss enable

On systems with SELinux, like Fedora, you might see hidden errors. In that case, run this to set the security context for the binary:

sudo semanage fcontext -a -t bin_t "/usr/local/bin/dnss"
sudo restorecon -v /usr/local/bin/dnss

Listens on port 53 for DNS queries, resolves them using the given HTTPS URL.

# Use the default HTTPS URL (currently, dns.google):
dnss -enable_dns_to_https
# Use Cloudflare's 1.1.1.1:
dnss -enable_dns_to_https -https_upstream="https://1.1.1.1/dns-query"
# Use Google's dns.google:
dnss -enable_dns_to_https -https_upstream="https://dns.google/dns-query"
# Use the default HTTPS URL for all resolutions, except for domain "myhome"
# which is resolved via a local DNS server.
dnss -enable_dns_to_https -dns_server_for_domain="myhome:10.0.1.1:53"

Receives DNS over HTTPS requests, resolves them using the machine's configured DNS servers, and returns the replies. You will need to have certificates for the domains you want to serve.

Supports both DoH and JSON modes automatically, and the endpoints are /dns-query and /resolve.

# Serve DNS over HTTPS requests, take certificates from letsencrypt.
DOMAIN=yourdomain.com
dnss -enable_https_to_dns \
  -https_key=/etc/letsencrypt/live/$DOMAIN/privkey.pem \
  -https_cert=/etc/letsencrypt/live/$DOMAIN/fullchain.pem