โ† Back to overview
๐Ÿงญ Reference ยท DNS & filtering

Own DNS โ€” ad-free and split-horizon

DNS is the first stop of every connection โ€” so it runs on your own network. AdGuard Home filters ads and trackers for every device, resolves internal names locally, and sends everything else out encrypted. Deliberately redundant, so DNS never becomes a single point of failure.

DNS ยท network-wide & split-horizon
๐Ÿ“ฑ
Phone
๐Ÿ’ป
PC
๐Ÿ“บ
TV
๐Ÿ 
IoT
โ†“ every DNS query on the network
๐Ÿ›ก๏ธ
AdGuard Home
ร—2 redundant ยท network-wide
โœ• ads & trackers
โ†“ internal namesโ†“ public names
๐Ÿ Local zone
split-horizon: internal names resolved locally, stays on the LAN.
๐Ÿ”Encrypted upstream
everything else out via DoH / DoT โ€” no plaintext DNS.
Ad-free for every device ยท redundant, so DNS never becomes a single point of failure.

๐Ÿ›ก๏ธAdGuard Home as resolver

A network-wide DNS resolver with curated blocklists against ads, trackers and malicious domains. The protection applies to every device on the network โ€” phone, TV, IoT โ€” with no client software at all.

AdGuard Homeblocklistsnetwork-wide

๐Ÿ”€Split-horizon

Internal names resolve locally and stay on the LAN instead of "hairpinning" out over the public internet. Public names go out normally โ€” one config, two clean views.

split-horizonlocal zoneno hairpin

๐Ÿ”Encrypted upstreams

Requests that leave the network go out via DNS-over-HTTPS or DNS-over-TLS โ€” no more plaintext DNS. The provider sees much less, and tampering gets harder.

DoHDoTprivate

โ™ป๏ธBuilt redundant

DNS is critical infrastructure: if it fails, it feels like "the whole internet" is down. So two instances run โ€” if one drops, the other takes over without anyone noticing.

2 instancesfailovercritical infra
Stack in use
AdGuard HomeDoH / DoTsplit-horizonfailover instance