Settings
Runtime configuration and access.
Version
0.9.3-demo
Demo build
Uptime
11d 4h
Simulated
Memory
86 MB
24 goroutines
Cache hit rate
41.8%
112,904 entries
Effective configuration
Configuration lives in your YAML file and environment, so a deployment is reproducible from its config rather than from database state.
- Data directory
- /var/lib/dnsdaddy
- Query logging
- Enabled
- Log client IPs
- Enabled
- Query-log retention
- 14 days · 3,182,004 rows
- Statistics retention
- 180 days
- Answer cache
- Enabled · max 250,000 entries
- Feed refresh interval
- Every 4 hours
- Upstream mode
- DNS-over-TLS, strict
Change admin password
Disabled in the demo — no account exists.
API tokens
Simulated tokens — no secrets are shown or issued here.
| Name | Prefix | Created | Last used | |
|---|---|---|---|---|
| grafana-scraper | dnsd_7f2a… | 2026-06-02 | 2026-08-11 | demo |
| weekly-report-cron | dnsd_c410… | 2026-05-19 | 2026-08-10 | demo |
The real management API is documented by the OpenAPI spec served at /openapi.yaml — see the repository.
About this project
DNS Daddy is an experimental, self-hosted protective DNS resolver, free and open source, and built as a learning and research project with extensive AI assistance. It is not independently audited and makes no guarantees of security. Please read the code, kick the tyres, and report what you find.