Written 5 Sep 2026. This is a how-to, not a product card.

See what Pi-hole blocked

Open the query log (or watch it over SSH) so you can tell ads are dying, which device asked, and which name to allow later. You don't need a new router.

Haven't installed the house ad block yet? Start with the first useful thing. Ads are back on every device? That checklist is when ads come back. One bank page broken while ads stay gone? That is when a site won't load after Pi-hole. This note is the calmer look: prove Pi-hole is answering, and read what it skipped.

Skip until the house asks Pi-hole

If phones never dropped ads, point DNS first: point common home routers at Pi-hole. Admin page blank? when the Pi-hole admin page won't open. You need house Wi-Fi (or a cable on the laptop), not guest Wi-Fi that still uses ISP DNS, and not cellular data on a phone.

What this is

Every time a phone or laptop asks for a name, Pi-hole writes a line. Allowed names go through. Blocked names never reach the ad server. The query log is that list. The dashboard totals are the short version. You are not buying a monitoring box. You are reading the diary the computer already keeps.

Step 1: open the dashboard

On a laptop or phone on the house network, open:

http://pi.hole/admin

Or the computer's address plus /admin. Sign in with the admin password. Forgot it? Change the Pi-hole admin password. You should see totals for total queries, queries blocked, and a percent blocked. A quiet house still shows some blocked names after a few minutes of browsing. Zero forever usually means the device is not using Pi-hole DNS yet.

Step 2: open the query log

In the admin menu, open Query Log (sometimes under Tools, depending on your Pi-hole version). Reload a news site or open a few apps on a phone that uses house DNS. New rows should appear. Look for:

Green / permitted / OK — the name was allowed.
Red / blocked / gravity / regex — Pi-hole skipped that name.
Client — which phone or laptop asked (often an address or a hostname).

Blocked rows with names like ads., doubleclick, googlesyndication, or similar tracker hosts are normal. That is the job working. You do not need to allow those.

Step 3: watch live over SSH (optional)

From the couch, SSH into the computer, then:

pihole tail

Reload a page on your phone. New lines scroll as names are asked. Press Ctrl-C when you have seen enough. To ask whether one name is on a list:

pihole query tracker.example.com

Swap in a real name from the log. This does not change anything. It only reports.

Step 4: read the dashboard for a week, not a minute

One quiet minute can look empty. Leave Pi-hole alone for a day of normal phone use, then open the dashboard again. Percent blocked in the teens or twenties is common. A huge spike after you added ten third-party lists is a clue you over-blocked, not a score to chase. Prefer the default lists until a real site breaks.

When a name you need is blocked

Do not turn blocking off forever from this page. Pause for five minutes, find the exact domain, then allow that one name. Full walk: when a site won't load after Pi-hole.

What this is not

This is not a fix when ads never dropped. It is not Unbound, Docker, or a second Pi. It is not opening the admin page past the house network. It is not a reason to stack a dozen block lists on day one. It is not buying a Raspberry Pi so the log looks “official.”

What next

Change the printed admin password if you have not: change the Pi-hole admin password. Once a week, keep Pi-hole updated. Tired of typing the number? Add a local name in Pi-hole. Before a scary reinstall, save a Pi-hole backup. A file share on this same computer can wait: a file share.

Optional: jot that Pi-hole is blocking in Lab plan — username + passkey, no email. Skip if you just want to keep reading.

Skip

Skip buying a mesh kit because the log looked quiet for thirty seconds.
Skip opening the admin UI to the internet.
Skip allowing every blocked tracker “just in case.”
Skip stacking extra block lists before you can read this log.
Skip this if ads are back on every device. That is a different walk.
Skip a new Raspberry Pi for a query log you already have.

Sources

Pi-hole docs. Pi-hole command (query, tail, status). Official pages only. For install, see the first useful thing. For a broken site, see when a site won't load after Pi-hole. For ads returning house-wide, see when ads come back. For router DNS, see point common home routers at Pi-hole.

Also on this topic

The first useful thingPut a house-wide ad block on the old PC. The rest of the house keeps using the internet as usual. You don't need a Raspberry Pi. When ads come backAds are back, sites won't load, or a phone still shows banners. Check the computer, Pi-hole, router DNS, then the phone. When a site won't load after Pi-holeA bank, streamer, or login page breaks after Pi-hole. Pause blocking for five minutes, then allow the domain you need. You don't need a new router. When one phone still shows adsEveryone else's ads dropped. One phone still shows banners. Check Private DNS, Private Relay, a VPN, then the Wi-Fi lease. You don't need a new router. Keep Pi-hole updatedWeekly apt does not refresh Pi-hole. Update the software and the block lists on the old PC so ads stay gone. You don't need a new Raspberry Pi. Add a local name in Pi-holeGive the old PC a short house name so phones and laptops can open SSH, the share, and the admin page without remembering the number. You don't need a new router. When the Pi-hole admin page won't openhttp://pi.hole/admin or the computer's address plus /admin won't load. Check house Wi-Fi, the address, then Pi-hole and the web service. You don't need a new router. Point common home routers at Pi-holeWhere to set DNS on TP-Link, ASUS, eero, Netgear, Nest, and ISP gateways so the house asks Pi-hole. Prefer LAN DHCP DNS. You don't need a new router. Change the Pi-hole admin passwordAfter the house ad block is up, change the admin password the installer printed. That password is not the login. Save a Pi-hole backup before you change thingsExport settings with Teleporter so a reinstall or a bad list does not wipe your allow list and local DNS. You don't need a new Raspberry Pi.