Unbound
Table of Contents
1. Description
Unbound is a validating, recursive, caching DNS resolver.
2. Configuration
Using Unbound and Pi-hole on DietPi (installed with dietpi-software)
diff -u --label \#\<buffer\ dietpi.conf.dpkg-dist\> --label \#\<buffer\ dietpi.conf\</ssh\:framboise\:\>\> /tmp/buffer-content-dDEBjp /tmp/buffer-content-zByEwJ --- #<buffer dietpi.conf.dpkg-dist> +++ #<buffer dietpi.conf</ssh:framboise:>> @@ -1,6 +1,9 @@ # https://unbound.docs.nlnetlabs.nl/en/latest/manpages/unbound.conf.html # At best, apply changes with an own config file like /etc/unbound/unbound.conf.d/local.conf. server: + # Do not daemonize, to allow proper systemd service control and status estimation. + do-daemonize: no + # A single thread is pretty sufficient for home or small office instances. #num-threads: 1 @@ -14,9 +17,9 @@ # Set "interface: 127.0.0.1" to listen on requests from the same machine only, useful in combination with Pi-hole/AdGuard Home. # Add an additional "interface: ::0" or "interface: ::1" respectively to listen on IPv6 requests. # The default is "interface: 127.0.0.1" and "interface: ::1" both. - #interface: 127.0.0.1 + interface: 127.0.0.1 # Default DNS port is "53". When used with Pi-hole/AdGuard Home, set this to e.g. "5335", since "5353" is used by mDNS already. - #port: 53 + port: 5335 # Control IP ranges which should be able to use this Unbound instance. # The DietPi defaults permit access from official local network IP ranges only, hence requests from www are denied. @@ -44,7 +47,7 @@ #do-udp: yes #do-tcp: yes #do-ip4: yes - #do-ip6: yes + do-ip6: no # Maximum number of queries per second ratelimit: 1000 Diff finished. Tue Sep 8 21:00:54 2026
DNS over TLS configuration file
# /etc/unbound/unbound.conf.d/dietpi-dot.conf server: # DNS over TLS tls-cert-bundle: /etc/ssl/certs/ca-certificates.crt forward-zone: name: "." forward-tls-upstream: yes forward-addr: 9.9.9.9@853#dns.quad9.net