Pi-hole review — network-wide DNS adblocker

Pi-hole is a network-wide adblocker that works at the DNS level. Instead of installing an extension per browser, Pi-hole blocks ads and trackers for every device on your network — including your smart TV, your phone, and IoT devices that don’t support browser extensions.

Pi-hole review — network-wide DNS adblocker

Pi-hole review

Pi-hole is a network-wide adblocker that works at the DNS level. Instead of installing an extension per browser, Pi-hole blocks ads and trackers for every device on your network — including your smart TV, your phone, and IoT devices that don’t support browser extensions.

Who is this for? Anyone who wants DNS-level blocking for the entire network on a Raspberry Pi or server. AdGuard Home is the main alternative, with encrypted DNS built in and a Dutch interface — compare both before choosing.


How Pi-hole works

When a device on your network looks up a domain name (e.g., ads.doubleclick.net), that request normally goes to a DNS server from your ISP or Google. With Pi-hole, your devices send that request to Pi-hole instead, and it checks its blocklists: if the domain is blocked, Pi-hole answers with the “unspecified address” 0.0.0.0 (or :: for IPv6), its default blocking mode. The connection never gets established. Anything not blocked, Pi-hole passes on to an upstream DNS server of your choice.

It is like the blocklists of a browser adblocker such as uBlock Origin, but for the entire network in one place, and per domain only.


Pi-hole vs AdGuard Home

Both do the same thing at their core: DNS-based ad-blocking for the network. Pi-hole is the older project (on GitHub since 2014, AdGuard Home since 2016), with more GitHub stars (about 62,000 against 38,000 on 7 November 2026), its own forum and extensive documentation. AdGuard Home builds more in, such as encrypted upstream DNS, and says it aims to be simple enough for casual users.

Pi-hole AdGuard Home
Interface Functional (English only) Modern, also in Dutch
Installation Script / Docker Script / Docker / Snap / binary
Blocklist management Extensive Extensive
DoH/DoT upstream Needs extra software (e.g. dnscrypt-proxy) Built-in (also DoQ, DNSCrypt)
Community About 62,000 GitHub stars, own forum About 38,000 GitHub stars
Open-source Yes (EUPL) Yes (GPLv3)

If choosing now: for new installations we recommend AdGuard Home — DNS-over-HTTPS without extra software. Pi-hole is a solid choice if you’re already familiar with the ecosystem.


Installation

Despite the name, Pi-hole is not limited to a Raspberry Pi. Officially supported are Raspberry Pi OS, Debian, Ubuntu, Fedora, CentOS Stream, Alpine and Armbian, on x86, ARM and RISC-V. Pi-hole’s stated minimum is 512 MB of RAM and 2 GB of free storage (4 GB recommended), and the machine needs a fixed IP address (a DHCP reservation in your router is fine).

Installation options:

  • Raspberry Pi — the classic choice; Raspberry Pi OS is on Pi-hole’s supported list
  • Docker — ideal on an existing NAS or homelab server
  • VM — on a Proxmox or VirtualBox installation
  • VPS — only behind a VPN such as WireGuard. Pi-hole’s docs say it was designed for a local network, and by default it only answers devices on its own subnet. Pi-hole warns that answering everyone makes it an open resolver, which can be abused for attacks

Installation via the official script (see pi-hole.net):

curl -sSL https://install.pi-hole.net | bash

Pi-hole’s own README calls piping to bash “controversial” because you can’t read the code first, and offers alternatives: download the script, read it, then run it.

wget -O basic-install.sh https://install.pi-hole.net
sudo bash basic-install.sh

The script is for a regular Linux install. On Docker you use Pi-hole’s official image instead (see “Docker” under Getting started).

Then set Pi-hole as the DNS server on your router. All devices on the network use it automatically — usually via your router’s DHCP settings, where you set the Pi-hole’s IP address as the (only) DNS server.

Router DHCP settings with the Pi-hole's IP address entered as Static DNS 1, the other DNS fields left blank


Blocklists

During installation Pi-hole offers one list: StevenBlack’s Unified Hosts List. You add more lists in the web interface under Group Management → Lists.

The Pi-hole dashboard showing total DNS queries, percent blocked, and the number of domains on the blocklist

Screenshot: Pi-hole 5, before February 2025.

Popular additions:

  • Steven Black hosts — combined list from multiple sources; the default list held 77,758 domains on 1 November 2026
  • Firebog — curated collection of categorised lists; the ones marked with a green tick are, according to Firebog, the least likely to interfere with browsing
  • oisd.nl — says it “prioritizes functionality over blocking”; the big list held 232,079 entries on 7 November 2026

Lists overlap, so the total is less than the sum. The dashboard shows how many domains your Pi-hole blocks in total.


What Pi-hole doesn’t do

Pi-hole works at the DNS level. Ads served via the same domain as the content (e.g., YouTube ads on youtube.com) are not blocked — for that you need a browser extension like uBlock Origin.

Pi-hole also only protects devices on your home network. On mobile data or an external Wi-Fi network, it doesn’t work.


Caveats

Always-on hardware required: Pi-hole must be running while your network depends on it. If the host goes down or restarts, devices lose DNS until it is back or you point the router elsewhere. A public DNS server as “second” DNS on the router isn’t a fix: Pi-hole’s own FAQ says Pi-hole must be the only DNS server, because devices may use the other one and skip the blocking.

DNS encryption: By default, Pi-hole sends DNS queries unencrypted to upstream servers, and it can’t encrypt them itself. Pi-hole’s docs describe two add-ons: dnscrypt-proxy sends queries encrypted (DNS-over-HTTPS or DNSCrypt) to a provider such as Quad9; Unbound makes Pi-hole its own resolver, so no single provider sees all your lookups, but in Pi-hole’s setup the queries Unbound sends out are plain, unencrypted DNS, so your internet provider can still see them. The older cloudflared route is deprecated: Cloudflare removed the proxy-dns feature it relies on from cloudflared releases since 2 February 2026, and Pi-hole no longer recommends it for new installations. For choosing a provider, see the privacy DNS guide.

IPv6: if your network uses IPv6, your router may also hand out its own IPv6 DNS server, and devices can use that one and skip Pi-hole. Check your router’s IPv6 or DHCPv6 settings; Pi-hole’s router pages show how for some routers.


Pros and cons

Pros

  • Blocks ads and trackers at DNS level for every device on the network — including smart TVs and IoT devices that cannot run their own adblocker
  • Blocklists of your choice, from StevenBlack’s default list to oisd or the Firebog collection
  • Runs on the main Linux distributions — Raspberry Pi, Docker on a NAS, VM, or a VPS behind a VPN
  • Long-running project with its own forum and extensive documentation
  • Free and open-source (EUPL); according to its README, built by volunteer developers and paid for by donations
  • Works well if you already have a Raspberry Pi or always-on server

Cons

  • Requires always-on hardware — if the host goes down, DNS stops working until you recover or point the router elsewhere
  • DNS queries are sent unencrypted to upstream servers by default — DoH needs extra software (dnscrypt-proxy)
  • YouTube ads and trackers on the same domain as the content cannot be blocked at DNS level
  • Only protects devices on your home network — not mobile data or external Wi-Fi by itself
  • Web interface in English only

Conclusion

Pi-hole is a proven tool for network-wide ad-blocking. If you already have a Raspberry Pi or always-on server, the installation barrier is low and the result is immediately noticeable.

For new installations we lean towards AdGuard Home: encrypted upstream DNS and a Dutch interface without extra software. Both are free and open-source.


Getting started

These steps were checked against Pi-hole 6.5 (FTL 6.8, web interface 6.6.1, released 17 October 2026) and Docker image 2026.10.1. The web interface is English-only.

1. Give the machine a fixed IP address

Set a DHCP reservation for it in your router (or a static address on the machine). The installer asks you to confirm this first (“Static IP Needed”).

2. Install Pi-hole

Run the install script on the machine (see Installation above for the read-first variant):

curl -sSL https://install.pi-hole.net | bash

The installer asks, in this order: which network interface to use, an upstream DNS provider (Quad9 is in the list; you can change it later), whether to add StevenBlack’s Unified Hosts List, whether to log queries, and a privacy mode. On a shared household network, think about the last two: with logging on and “Show everything”, the Query Log shows every lookup of every device in the house.

The “Installation Complete!” screen shows Pi-hole’s IP address and a random password for the web interface. Note the password; you can change it later with sudo pihole setpassword.

Docker instead: use the docker-compose.yml example from the official image’s README. Set your own password with FTLCONF_webserver_api_password (without it, a random password appears in the container log, docker logs pihole). Pre-v6 variables such as WEBPASSWORD no longer work. The example also sets FTLCONF_dns_listeningMode: 'ALL' for Docker’s bridge network; Pi-hole warns that this can make it an open resolver, so never open port 53 to the internet.

3. Open the web interface

Go to http://<Pi-hole-IP>/admin. http://pi.hole/admin only works once your device uses Pi-hole as its DNS server (step 4).

4. Set Pi-hole as DNS on your router

Log in to your router and find the LAN DHCP/DNS settings (not the internet/WAN DNS). Enter the Pi-hole’s IP address as the only DNS server and leave the other DNS fields empty. Write down your router’s own address first, so you can undo this if the Pi-hole is ever down. Devices pick up the change when they renew their DHCP lease; reconnecting them to the network is the quickest way. If your router has no DNS setting, Pi-hole can take over DHCP (Settings → DHCP → DHCP server enabled), but switch off your router’s DHCP server first, as Pi-hole’s own page warns. Pi-hole’s docs have router setup pages for some brands, including the Fritz!Box.

5. Add blocklists

In the web interface, go to Group Management → Lists. Paste a list URL into Address, for example https://big.oisd.nl or one of the Firebog tick lists, and click Add blocklist. Then go to Tools → Update Gravity and click Update to load the lists.

6. Check that it works

Open Query Log in the web interface and browse on a phone or laptop: its queries should appear with that device’s own address. If every query comes from your router’s address, the router is relaying DNS instead of handing out Pi-hole’s address: blocking still works, but you can’t see or manage devices separately.

7. Encrypt the upstream (optional)

Follow Pi-hole’s dnscrypt-proxy guide (DNS-over-HTTPS to a provider such as Quad9) or its Unbound guide (your own resolver). Then go to Settings → DNS, untick all servers under Upstream DNS Servers, enter 127.0.0.1#5053 (dnscrypt-proxy) or 127.0.0.1#5335 (Unbound) under Custom DNS servers, and click Save & Apply. Skip Pi-hole’s cloudflared guide: it is deprecated.


Already have a setup?

Pi-hole 5 to 6. Pi-hole 6 (2025) replaced a lot under the hood. Update with pihole -up after reading the release notes; Pi-hole’s own docs advise this “especially” for v5 to v6. What changes:

  • Settings move from setupVars.conf and the files in /etc/dnsmasq.d/ into one file, /etc/pihole/pihole.toml; the old files are kept in /etc/pihole/migration_backup_v6. Your password carries over.
  • Pi-hole now has its own web server; the installer offers to switch off lighttpd. If you kept custom lighttpd settings, Pi-hole’s web interface may move to port 8080.
  • Your own extra files in /etc/dnsmasq.d/ are no longer read unless you switch that on (misc.etc_dnsmasq_d).
  • The old API (/admin/api.php) is gone; apps and scripts that used it need the new API.
  • Commands changed: pihole -a -p is now pihole setpassword, and blocklists live under Group Management → Lists (formerly Adlists).
  • Docker: almost all environment variables were replaced by FTLCONF_ variables (for example WEBPASSWORD → FTLCONF_webserver_api_password); see Pi-hole’s Docker v5 to v6 page.

Already on Pi-hole 6: keep it updated. According to the release notes of Pi-hole’s Docker image, the 17 October 2026 releases fixed 17 security advisories across Core, FTL and the web interface.


Next step

Chosen Pi-hole?

  • Privacy DNS guide — which upstream provider to choose, and what DNS encryption does and doesn’t hide

Similar options

Want to go further?