Published November 9, 2026

Best Open Source Network-Wide Ad Blockers in 2026 (DNS-Level)

A network-wide ad blocker is a small DNS server on your own network that answers every device's lookups and refuses to resolve known ad and tracker domains, so phones, smart TVs and consoles are covered without installing anything on them. For most homes the right pick in 2026 is AdGuard Home; Pi-hole has the largest community, and Blocky or Technitium DNS Server suit people who want a leaner or a more complete DNS server. This guide ranks eight tools by where the blocking happens. Star counts come from our directory.

A word of honesty: DNS-level blocking refuses to resolve a domain, so it cannot touch ads served from the same domain as the content. Pi-hole's FAQ says YouTube "ads are typically served from the same domain as the video is" and that "it's not likely that you'll be able to block in-video ads with Pi-hole" (Pi-hole FAQ); Facebook and Instagram feed ads "share the same domain and API endpoints as legitimate content" (adblock-tester). Nor can it see queries that never reach it: a Chromecast asking Google's 8.8.8.8 directly, or an app with its own DoH resolver, bypasses it; pfSense's docs warn that "clients using DNS over TLS or DNS over HTTPS could circumvent this protection" (Netgate docs).

TL;DR — pick by where you want blocking to happen

  • LAN, every device, encrypted DNS built in → AdGuard Home
  • LAN, biggest community, smallest hardware → Pi-hole
  • LAN, one YAML file, no dashboard → Blocky
  • LAN, plus a full DNS server → Technitium DNS Server
  • Upstream, resolving names yourself → Unbound
  • Upstream, encrypted hop to a provider → dnscrypt-proxy
  • Phone on mobile data → Rethink DNS or AdAway
  • Browser, as a complement → uBlock Origin in Firefox

Key takeaways

You want…Pick
The best DNS ad blocker for most homesAdGuard Home
The largest community and the lowest hardware barPi-hole
The lightest sinkhole, one YAML fileBlocky
A full DNS server that also blocksTechnitium DNS Server
A private recursive upstreamUnbound
Encrypted upstream for Pi-hole after cloudflareddnscrypt-proxy
Blocking on an Android phone away from homeRethink DNS or AdAway
Cosmetic and same-domain ads DNS cannot touchuBlock Origin (Firefox)

The three layers of network-wide ad blocking

1. An ad blocking DNS server on your LAN (the sinkhole)

Your router hands every device the sinkhole's address; the sinkhole answers from cache or an upstream and returns nothing useful for listed domains, which AdGuard Home's README calls "the so-called 'DNS sinkholing' method" (AdGuard Home README). Pi-hole, AdGuard Home, Blocky and Technitium DNS Server live here.

2. An encrypted upstream resolver you run yourself

The sinkhole still needs answers, and by default a public resolver provides them and sees every domain you look up; Pi-hole's Unbound guide asks "Whom can you trust?" (Pi-hole Unbound guide). Unbound is a recursive resolver that walks the DNS tree from the root servers itself; dnscrypt-proxy encrypts the hop to a provider you choose. AdGuard Home, Blocky and Technitium speak DoH, DoT and DoQ upstream natively; Pi-hole does not, and its cloudflared guide now warns that "as of November 2025 the proxy-dns feature that this guide relies upon is deprecated by cloudflare" (Pi-hole cloudflared guide). Prefer a hosted filter? See our open source alternatives to NextDNS.

3. On-device fallbacks for phones and laptops that leave the house

A LAN sinkhole stops working when a phone switches to mobile data. Either expose the sinkhole's DoH endpoint and point the phone at it, or block on the device: Rethink DNS routes app lookups to a resolver you choose, while AdAway and personalDNSfilter apply lists through a hosts file or local VPN. In the browser, uBlock Origin handles the cosmetic and same-domain ads DNS cannot; since Chrome's timeline shows "all remaining Manifest V2 extensions" removed from the Chrome Web Store on 31 August 2026 (Chrome MV2 timeline) and uBlock Origin's README records "Chrome Web Store: Removed on 2026-08-31" (uBlock Origin), that means Firefox.

How we evaluated

  • Adoption — GitHub stars: our directory for the sinkholes, the GitHub API (9 November 2026) for the rest.
  • Maintenance — month of last commit; every project shipped code in 2026.
  • Deployment — Raspberry Pi, Docker and routers, per the project's docs.
  • DNS features — DoH/DoT/DoQ as server and upstream, per-client rules, blocklist formats, parental controls.

Quick comparison

NameLayerRuns onEncrypted DNS (DoH/DoT/DoQ)Per-client rulesStarsLanguage
AdGuard HomeLAN sinkholeLinux, macOS, Windows, BSD, DockerServer + upstream: DoH, DoT, DoQYes (IP, CIDR, MAC, ClientID)36KGo
Pi-holeLAN sinkholeLinux, Docker; armv6 to riscv64None built inYes (groups)60KShell
BlockyLAN sinkholeDocker, x86-64, ARM, MIPS, OpenWrtServer: DoH, DoT; upstream: DoH, DoT, DoQYes (client groups)6.8KGo
Technitium DNS ServerSinkhole + full DNS serverWindows, Linux, macOS, Pi (arm7+), DockerServer + forwarder: DoH, DoT, DoQYes (per IP or subnet)9.0KC#
UnboundUpstream resolverLinux, BSD, macOSDoT, DoH—5.1KC
dnscrypt-proxyUpstream relayLinux, macOS, Windows, BSD, AndroidClient: DoH, DNSCrypt, ODoH—14KGo
Rethink DNSOn-device (Android)AndroidClient: DoH, DoT, DNSCrypt, ODoHPer app5.9KKotlin
AdAwayOn-device (Android)Android 8+——9.6KC

The best open source network-wide ad blockers, ranked

1. AdGuard Home — the complete sinkhole

Best for: most homes; everything built in. Skip if: you want Pi-hole's community or Blocky's footprint.

AdGuard Home sinkholes DNS like Pi-hole; its README's comparison table lists what it adds: encrypted upstreams, a DoH or DoT server, phishing blocking, parental control, safe search and access control, where Pi-hole "requires additional software" (AdGuard Home README). DoQ works "out-of-the-box" with a Let's Encrypt certificate (Encryption wiki), and clients get their own rules by IP, CIDR, MAC or a ClientID that works over DoH (Clients wiki). See also our open source alternatives to AdGuard Home.

  • Key features: DoH/DoT/DoQ server and upstream · per-client rules · parental control · DHCP
  • Pros: the most complete sinkhole · builds from ARMv5 to Windows
  • Cons: the GitHub wiki is marked outdated · encrypted serving needs a certificate
  • Stars: 36K · Language: Go · License: GPL-3.0 · Last updated: 2026-08
  • 🔗 Details & alternatives →

2. Pi-hole — the community standard

Best for: the largest community and the oldest Raspberry Pi in the drawer. Skip if: you want encrypted DNS without a second program.

Pi-hole made network-wide blocking a hobbyist standard. Its resolver pihole-FTL is based on dnsmasq and also provides DHCP and the web server (FTL docs); version 6 (February 2025) folded the web interface and REST API into it (Pi-hole v6 announcement). Per-client rules work through groups (group management examples). It needs 512 MB of RAM and 2 GB of disk, with binaries from armv6 to riscv64 (prerequisites), and by default answers NXDOMAIN for use-application-dns.net and mask.icloud.com to stop Firefox DoH and iCloud Private Relay bypassing it (config reference). See it in our best self-hosted apps guide, or our open source alternatives to Pi-hole.

  • Key features: dnsmasq-based FTL with DHCP · group-based per-client rules · REST API
  • Pros: the largest community · the lowest hardware bar · pihole -up
  • Cons: no built-in DoH/DoT/DoQ · parental control "requires non-default blocklists"
  • Stars: 60K · Language: Shell · License: — · Last updated: 2026-07
  • 🔗 Details & alternatives →

3. Blocky — the lightweight, config-driven sinkhole

Best for: people who prefer a YAML file to a dashboard. Skip if: you want a web UI.

Blocky is a "fast and lightweight DNS proxy as ad-blocker for local network" with allow and deny lists "per client group (Kids, Smart home devices, etc.)", per-group upstreams and Prometheus metrics (Blocky docs). It serves DoT on ports.tls and DoH on its HTTP and HTTPS listeners, and takes https, tcp-tls or quic upstreams (configuration reference). Config is a single config.yml; the docs list a REST API and CLI, not a dashboard.

  • Key features: per-client-group lists and upstreams · DoT and DoH endpoints · DoQ upstreams · Prometheus metrics
  • Pros: single small binary · infrastructure-as-code friendly · runs on routers
  • Cons: no web UI · no parental-control presets
  • Stars: 6.8K · Language: Go · License: Apache-2.0 · Last updated: 2026-07
  • 🔗 Details & alternatives →

4. Technitium DNS Server — the full DNS server that also blocks

Best for: a full DNS server that also blocks. Skip if: you only want a sinkhole, or run a Pi 1 or Zero.

Technitium DNS Server is "an open source authoritative as well as recursive DNS server", a .NET 10 application with "a user friendly web console" (Technitium features). Its Advanced Blocking app applies "different block lists for different client IP addresses or subnet", and you can "self host DNS-over-TLS, DNS-over-HTTPS, and DNS-over-QUIC DNS services on your network" and use all three for forwarders. It "works on Windows, Linux, macOS and Raspberry Pi" (arm7+).

  • Key features: authoritative + recursive · DoT/DoH/DoQ server and forwarders · DNSSEC · DHCP
  • Pros: the broadest DNS feature set here · native Windows support
  • Cons: needs the .NET runtime · no armv6 build
  • Stars: 9.0K · Language: C# · License: GPL-3.0 · Last updated: 2026-06
  • 🔗 Details & alternatives →

5. Unbound — the recursive resolver behind your sinkhole

Best for: keeping lookups away from public resolvers. Skip if: you expect it to block ads on its own.

Unbound is "a validating, recursive, caching DNS resolver" from NLnet Labs "under the BSD license" that "supports DNS-over-TLS and DNS-over-HTTPS" (NLnet Labs). It walks the DNS tree from the root servers itself; Pi-hole's guide pairs the two on port 5335 so no single upstream sees your query history. The guide admits "the first request to a formerly unknown TLD may take up to a second" before caching takes over (Pi-hole Unbound guide).

  • Key features: recursive resolution from the root · DNSSEC validation · caching · DoT and DoH
  • Pros: no upstream provider sees your lookups · documented by Pi-hole
  • Cons: slower first lookups · no blocking of its own
  • Stars: 5.1K · Language: C · License: BSD-3-Clause · Last updated: 2026-11
  • 🔗 Official site → (not in our directory yet)

6. dnscrypt-proxy — the encrypted upstream relay

Best for: Pi-hole users who lost cloudflared. Skip if: you already run Unbound.

dnscrypt-proxy is "a flexible DNS proxy, with support for modern encrypted DNS protocols": DoH, DNSCrypt, Anonymized DNS and ODoH, ISC-licensed, for Linux, macOS, Windows, BSD and Android (dnscrypt-proxy README). Pi-hole's guide runs it on port 5053 as the upstream to prevent "man-in-the-middle attacks between Pi-hole and upstream DNS servers" (Pi-hole dnscrypt-proxy guide).

  • Key features: DoH, DNSCrypt, Anonymized DNS, ODoH · built-in filtering · caching
  • Pros: the simplest way to encrypt the upstream hop · many public relays
  • Cons: you still trust the resolver you pick
  • Stars: 14K · Language: Go · License: ISC · Last updated: 2026-11
  • 🔗 Official site → (not in our directory yet)

7. Rethink DNS — the Android layer for when you leave home

Best for: keeping the home sinkhole on the phone over mobile data. Skip if: you want a plain hosts-file blocker (see AdAway).

Rethink DNS + Firewall is an Apache-2.0 Android app, "a multi-hop WireGuard client, an OpenSnitch-inspired firewall and network monitor" with DoH, ODoH, DoT and DNSCrypt clients (Rethink README). In DNS mode it sends app lookups to a resolver you choose, which can be your own sinkhole's DoH endpoint, and its firewall blocks per app without root.

  • Key features: DoH/DoT/DNSCrypt/ODoH client · custom resolver · per-app firewall
  • Pros: no root · keeps home-network rules on the road
  • Cons: Android only · more than ad blocking alone needs
  • Stars: 5.9K · Language: Kotlin · License: Apache-2.0 · Last updated: 2026-11
  • 🔗 Official site → (not in our directory yet)

8. AdAway — the hosts-file classic for Android

Best for: simple list-based blocking on Android, rooted or not. Skip if: you want DNS encryption or per-app control (see Rethink DNS).

AdAway is "an open source ad blocker for Android using the hosts file and local vpn", GPLv3+ (AdAway README). Rooted phones use the hosts file; everyone else uses VPN mode, "root not required with local VPN mode". Version 5 needs "Android 8 and above" and ships through F-Droid rather than Google Play (adaway.org).

  • Key features: hosts-file or local-VPN blocking · Magisk systemless hosts · F-Droid builds
  • Pros: simple · works with or without root
  • Cons: Android only · no encrypted DNS
  • Stars: 9.6K · Language: C · License: GPL-3.0 · Last updated: 2026-11
  • 🔗 Official site → (not in our directory yet)

Also worth knowing

  • personalDNSfilter — "a DNS filter proxy written in Java" over a local VPN, no root; GPL-2.0, 954 stars, updated on F-Droid 25 October 2026 (F-Droid).
  • hBlock (MIT, 2.0K stars) and maza-ad-blocking (Apache-2.0, 1.9K stars) build a blocking hosts file on a laptop or desktop instead; hBlock "replaces the hosts file of your system" (hBlock README).
  • uBlock Origin — 69K stars, GPL-3.0, the most-starred open source ad blocker on this page.

Pi-hole vs AdGuard Home: the choice most people actually face

Encrypted DNS. AdGuard Home serves DoH, DoT and DoQ and uses encrypted upstreams out of the box; its README marks both as "requires additional software" for Pi-hole, whose path is Unbound or dnscrypt-proxy.

Per-client settings. AdGuard Home identifies clients by IP, CIDR, MAC or a ClientID that works over DoH, DoT and DoQ; Pi-hole uses groups, with clients identified by IP address in its documented examples.

Parental controls. Built into AdGuard Home, with safe search; for Pi-hole the README says parental control "requires non-default blocklists".

Blocklist formats. AdGuard Home recommends adblock-style rules (||example.org^) and reads hosts and domain lists; Pi-hole's installer offers StevenBlack's hosts file, and v6 added subscribed allowlists.

Update model. AdGuard Home updates from the "Update now" button or --update, except in Docker and Snap, where you replace the image (Getting Started); Pi-hole updates with pihole -up (Pi-hole update docs).

Web UI and hardware. Both have one: AdGuard Home's on port 80 after a port-3000 setup wizard, Pi-hole v6's from the FTL binary with native HTTPS. Pi-hole publishes a floor of 512 MB of RAM and 2 GB of disk; AdGuard Home publishes no minimum but ships builds down to ARMv5 and 32-bit MIPS (Platforms wiki).

Verdict: AdGuard Home for encrypted DNS and parental controls without a second program; Pi-hole for the community and the lowest hardware bar, plus Unbound or dnscrypt-proxy.

Blocklists: the part nobody tells you about

Pi-hole's installer offers one list, StevenBlack's Unified Hosts, which its README counts at 78,215 entries (StevenBlack/hosts). AdGuard Home enables one, "AdGuard DNS filter", whose header says it is "simplified specifically to be better compatible with DNS-level ad blocking" (AdGuard DNS filter); the copy we pulled on 9 November 2026 had roughly 188,000 rules.

Aggressive telemetry lists are where things break. Pi-hole's community page of commonly whitelisted domains lists Windows Update entries such as tlu.dl.delivery.mp.microsoft.com ("Without the follwing Whitelist Entrys Windows10 update can't be completed"), clientconfig.passport.net for Xbox Live sign-ins and android.clients.google.com for Google Play (commonly whitelisted domains). For Samsung TVs, user reports on the Pi-hole forum and Control D's board point at cdn.samsungcloudsolution.com: an IoT telemetry filter blocking it broke the TV's internet test and update check (Control D discussion).

Quality beats quantity. The oisd list "prioritizes functionality over blocking" and targets telemetry only "where not needed for proper functionality" (oisd). Start with the default list plus one curated list and allowlist what breaks.

How to deploy it

Raspberry Pi. All four sinkholes run on one: Pi-hole from armv6 up (even a Pi Zero), AdGuard Home with ARMv6, ARMv7 and 64-bit ARM builds, Blocky ("runs fine on Raspberry PI") and Technitium from arm7. The same Pi can also run a music server.

Docker. All four have official images: pihole/pihole (Pi-hole Docker docs), adguard/adguardhome, Blocky and Technitium.

Router. AdGuard Home publishes MIPS and ARM builds and its README links an OpenWrt LuCI app and a GL.iNet guide; Blocky's docs say it runs on OpenWrt routers; Pi-hole and Technitium expect a Linux box or Docker.

The gotcha: hard-coded DNS. Some devices ignore the DNS server your router hands out. A Pi-hole community packet capture from 2018 found that a "chromecast tries to get info from 8.8.8.8 (google DNS)", and the fix was a NAT rule so that "all DNS requests (port 53) to 8.8.8.8 and 8.8.4.4 are redirected to my pihole" (Pi-hole forum). pfSense's recipe forwards every LAN packet for port 53 to the firewall's resolver so that "access to other DNS servers on port 53 is impossible" (Netgate: DNS redirect); port 853 (DoT) can be blocked the same way, while DoH "is harder to block as it uses port 443" (Netgate: blocking external DNS).

How to choose

  • "Just tell me what to install" → AdGuard Home in Docker.
  • Most help online, cheapest hardware → Pi-hole plus Unbound.
  • Compose files and Grafana → Blocky.
  • Authoritative zones and DHCP too → Technitium DNS Server.
  • A private upstream → Unbound, or dnscrypt-proxy for an encrypted provider.
  • A phone that leaves the house → Rethink DNS pointed at your DoH endpoint, or AdAway.
  • Ads DNS cannot touch → uBlock Origin in Firefox.

The best open source ad blocker for a whole household is a self hosted ad blocker at layer one, a private upstream at layer two, and uBlock Origin for the rest.

Frequently asked questions

What is a network-wide ad blocker? A DNS server on your own network that every device uses and that refuses to resolve domains on its blocklists, so phones, smart TVs and consoles are covered with nothing installed on them. AdGuard Home, Pi-hole, Blocky and Technitium are the open source examples.

What is the best DNS ad blocker for a home network? For most homes, AdGuard Home: encrypted DNS, parental control and per-client rules are built in. Choose Pi-hole for the largest community and lowest hardware bar, plus Unbound or dnscrypt-proxy for encrypted upstream DNS.

Does a DNS ad blocker block YouTube ads? No. Pi-hole's FAQ explains that YouTube "ads are typically served from the same domain as the video is", so there is nothing to block without blocking the video. YouTube also enforces directly: on 31 October 2023 a spokesperson told 9to5Google that "the use of ad blockers violate YouTube's Terms of Service" (9to5Google).

Do I need Unbound with Pi-hole? Not to block ads. You need it, or dnscrypt-proxy, if you care who sees your upstream lookups, because Pi-hole alone forwards unencrypted queries to a public resolver. Unbound replaces that resolver with your own on port 5335; dnscrypt-proxy encrypts the hop to a provider on port 5053.

What is the difference between DNS-level and browser ad blocking? DNS-level ad blocking stops a domain resolving for every device, but it cannot remove ads served from the content's own domain. A browser extension such as uBlock Origin sees the page itself, but only in that browser; use both, with the browser half in Firefox now that Chrome has dropped Manifest V2.

Can I run a network-wide ad blocker without a Raspberry Pi? Yes. Pi-hole's prerequisites say any hardware running a supported Linux distribution works, and every sinkhole here has an official Docker image, so a NAS, old laptop or VM qualifies. AdGuard Home and Blocky run on OpenWrt-class routers; Technitium runs on Windows.

Is DNS ad blocking legal, and does it break websites? Running your own resolver and choosing what it answers is ordinary network administration; nothing here bypasses a paywall. It does break things occasionally: Windows Update, Xbox Live sign-in and Samsung TV apps recur in allowlist threads. Watch the query log and allowlist what broke.

Sources

The bottom line

Network-wide blocking is the highest-leverage privacy change a household can make. Put AdGuard Home on the LAN unless you prefer Pi-hole's community or Blocky's minimalism, add Unbound or dnscrypt-proxy as a private upstream, redirect port 53 at the router, and keep uBlock Origin in Firefox for the ads that never touch DNS. All of it is free and shipped updates in 2026.

Browse open source alternatives to popular software, see the best self-hosted apps for the rest of your stack, or explore the full directory of open source projects.

Related articles