AdGuard and Unbound DNS
MRDTech uses AdGuard Home for DNS filtering and Unbound for internal recursive resolution.
Repository references:
Design
| Layer | Role |
|---|---|
| AdGuard Home | DNS filtering, blocklists, client visibility, policy enforcement |
| AdGuard Home Sync | Centralized synchronization between AdGuard nodes |
| Unbound | Recursive DNS resolver with DNSSEC-aware internal resolution |
| UniFi DHCP/DNS settings | Client DNS distribution |
Operating model
- Clients use AdGuard for filtering and visibility.
- AdGuard forwards recursive lookups to Unbound instead of relying on public resolvers directly.
- AdGuard Home Sync keeps filter lists and settings aligned between nodes.
- NOC Dashboard and weekly reports collect AdGuard block metrics and top blocked domains.
Monitoring
- NOC Dashboard includes AdGuard status and trend sparklines.
- Weekly infrastructure report includes top AdGuard blocked domains.
- AdGuard Home update status is visible through Home Assistant entities.
Security notes
- DNS filtering is a control, not a substitute for endpoint protection.
- Keep internal recursive resolution private to LAN/VPN segments.
- Do not expose AdGuard admin interfaces publicly without Zero Trust controls.