01 / THE ROLE
In this lab.
AdGuard Home runs as a containerised DNS-filtering service with persistent configuration and working data. Its statistics are integrated into the internal Homepage dashboard. BIND9 has a separate authoritative-DNS role; the two tools should not be described as interchangeable.
02 / THE CONNECTIONS
Follow the flow.
- STEP 01DNS request
- STEP 02Filtering policy
- STEP 03Resolution
- STEP 04Result & statistics
03 / How it works
How it works.
The filtering layer evaluates DNS requests against its configured policy and records useful statistics. Administration and query handling are separate interfaces. Configuration changes can affect many clients, so a working web page is not the only acceptance criterion.
04 / Persistent data & recovery
Persistent data & recovery.
Persistent configuration preserves filtering and resolver settings; working data may include query history and statistics. That history can reveal browsing patterns and remains private. Recovery should restore intended settings without assuming every retained query is essential state.
05 / How to check it
How to check it.
Test actual DNS resolution and an expected filtering outcome as well as the administrative interface. A dashboard widget reading statistics confirms that integration, not the full behaviour of every client or upstream resolver.
06 / Decisions & limits
Decisions & limits.
Filtering provides control and visibility, but adds a dependency to name resolution. The lab’s public material explains the role without publishing client identities, query logs or allow/block lists.