AdGuard Home
AdGuard Home: a first setup, important settings, verification, and recovery considerations.
Working directory: ~/homelab/core/dns-dhcp. Follow the common setup workflow first. This is a setup note based on the linked documentation, not a copy of my live configuration or a runtime verification of this full stack.
Start here
AdGuard Home can resolve and filter DNS queries. This folder name does not imply DHCP is enabled. Start with DNS for one test client. Do not replace the household resolver or enable a second DHCP server while learning; either can interrupt unrelated devices.
Settings and data
Persist the application's work and conf directories using the official paths. DNS needs UDP and TCP, normally port 53. Check sudo ss -luntp for conflicts before binding a port; do not disable the host resolver blindly. Keep the administration UI separate from client DNS access.
Check it
Query the new resolver explicitly from one allowed test client using dig @YOUR_DNS_SERVER example.org. Replace the placeholder with your own resolver address. Check the answer and query log, then test a deliberate block rule using a harmless domain you chose. Keep a known-good fallback setting for the client.
When something fails
Timeouts require checking both protocols, listener address, and firewall scope. Unexpected blocking needs the matching filter rule, not disabling all protection. Query logs reveal browsing patterns; limit access and retention. Back up configuration and document client rollback before changing router-wide DNS.