Setup
How devices point at DNS Daddy.
Resolver endpoints
Example addresses from documentation ranges — these do not resolve anything.
Plain DNS (UDP/TCP)
192.0.2.10:53
DNS-over-TLS
192.0.2.10:853
DNS-over-HTTPS
https://dns.example.com/dns-query
Dashboard
127.0.0.1:8080
Per-network DoH URLs
Each network gets a tokenised DoH path so roaming devices keep their policy.
| Network | Policy scope | DoH URL |
|---|---|---|
| Office | Enforcing | https://dns.example.com/dns-query/tok-hq-demo |
| Guest Wi-Fi | Enforcing | https://dns.example.com/dns-query/tok-guest-demo |
| Lab | Enforcing | https://dns.example.com/dns-query/tok-lab-demo |
| Roaming laptops | Enforcing | https://dns.example.com/dns-query/tok-roam-demo |
Upstream resolvers
Where DNS Daddy forwards what it does not block.
| Upstream | Protocol | Queries | Errors | Avg latency |
|---|---|---|---|---|
| tls://192.0.2.53:853#resolver-a.example.net | tls · encrypted | 148,902 | 41 | 18.4 ms |
| tls://198.51.100.53:853#resolver-b.example.net | tls · encrypted | 96,240 | 12 | 21.9 ms |
| https://203.0.113.53/dns-query | https · encrypted | 12,004 | 3 | 34.2 ms |
Ready to run this for real? Install DNS Daddy — Docker, systemd or from source. The dashboard binds to 127.0.0.1:8080 by default.