Network, AdGuard & remote access

Two upgrades make the whole house better: network-wide ad and tracker blocking with AdGuard Home, and private remote access with Tailscale. Both are easy, both are reversible, and both have exactly a few traps worth knowing first.

AdGuard Home on the NAS

Run AdGuard Home in Docker on the NAS, point your router's DNS at it, and every device in the house gets filtered DNS. Three rules keep it painless: never enable AdGuard's DHCP server (your router keeps that job), watch for the port-53 conflict with other containers, and remember the NAS becomes a single point of failure — if it is down, DNS is down, so add a secondary plan. Start with quality blocklists such as HaGeZi and OISD rather than piling on every list you find.

The trap: the IPv6 leak

On mesh systems including eero, IPv6 can silently hand your devices your ISP's resolvers alongside AdGuard — pages load, ads appear, and AdGuard's dashboard looks oddly quiet. After flipping DNS, test from a phone with manual DNS and check whether IPv6 lookups are bypassing the filter; fix the router's IPv6 DNS settings, not the blocklists.

Tailscale remote access, in the safe order

Tailscale gives you private access to Home Assistant from anywhere without opening ports. Build it in two stages: first a plain home exit node (your traffic exits on your home connection, filtered by your AdGuard DNS), and only later a VPN-flavoured exit node. The tempting shortcut — routing the exit node through a VPN container such as Gluetun — is fragile as commonly described: Gluetun rebuilds its firewall rules on every reconnect and silently drops forwarding, and the design needs namespace and settings work most guides omit. A proven pattern for stage two is the Tailbox/SOCKS approach; stage one alone covers most people permanently.

What never to do

Next: the full build list & costs.