Skip to main content

DNS and ad blocking

Recorded deployment: CT 102

The DNS role was originally Technitium and later targeted Pi-hole + Unbound. DNS availability is critical to the LAN.

Verification example​

dig example.com @192.168.1.53

Run this inside the relevant LXC, after confirming the application is installed and the command applies.

Security and operations​

Test DNS before switching router DHCP settings. Do not create a publicly accessible recursive resolver.

Documentation checklist​

  1. Record service purpose and dependencies.
  2. Save a redacted Compose file in Forgejo.
  3. Describe persistent volumes and backups.
  4. Add a health monitor in Uptime Kuma.
  5. Record upgrade and rollback procedures.