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

When the house won't browse after Pi-hole

Phones say no internet, or every site times out, after you pointed the house at Pi-hole. Put router DNS back on automatic so dinner works, then fix the computer. You don't need a new router.

Haven't installed Pi-hole yet? Start with the first useful thing. Sites load but ads are back? That is when ads come back. One bank or login broken while everything else is fine? That is when a site won't load after Pi-hole. Tabs hang a few seconds then paint? That is when browsing feels slow after Pi-hole. This note is the panic case: Wi-Fi is connected, but names won't resolve house-wide.

Skip until the router points DNS at the computer

If you never changed LAN / DHCP DNS on the house router, this page will not help. Pointing the house is point common home routers at Pi-hole, or the short pass point the house at the ad block. If only one phone is weird while others browse fine, that is closer to when one phone still shows ads.

What this is

When the router tells every phone and laptop to ask the old PC for names, and that PC is asleep, off, or Pi-hole is dead, the house looks like the internet died. Wi-Fi still shows connected. Apps time out. Some phones say “no internet.” You did not brick the router. You pointed DNS at a computer that stopped answering. Undo DNS first so people can browse. Fix the computer second. Point DNS back when it is healthy.

Step 1: calm check in thirty seconds

On a phone or laptop on house Wi-Fi, try a normal site (news, weather). Fail for everyone? Stay on this page. Only one device fails? Toggle airplane mode or forget/rejoin Wi-Fi once, then see when one phone still shows ads or when one laptop still shows ads.

From a laptop that still has any working path, try pinging a number (not a name):

ping -c 3 1.1.1.1

Replies mean the WAN path is often fine and DNS is the suspect. Total silence on every device, including the modem lights looking wrong, can be the ISP — wait a few minutes before you buy anything.

Step 2: put router DNS back on automatic (dinner fix)

Log into the house gateway the way you did when you set Pi-hole. Can't open the login page? When the home router page won't open. Password fails? When the router password won't work.

Find the same LAN / DHCP / DNS screen you changed before. Set DNS back to Automatic, Get from ISP, or clear the custom primary/secondary fields so the router hands out its own DNS again. Save. Reboot the router only if the maker page says you must.

On phones and laptops, toggle Wi-Fi off and on (or airplane mode) so they grab a fresh lease. Browse again. Sites should load. Ads will come back for now — that is fine. You bought calm for the house.

Brand menus for the same screens you used to point at Pi-hole live in point common home routers at Pi-hole (use the Undo idea there: automatic / ISP on the screen you changed).

Step 3: one-laptop escape if the router login itself is stuck

If the gateway page will not load because names are dead, try the gateway by number (sticker or ipconfig / ip route default). Prefer http:// plus that number on house Wi-Fi.

Still stuck? On one laptop only, set Wi-Fi DNS manually to 1.1.1.1 (and maybe 1.0.0.1), renew the lease, then open the router by number and put LAN DNS back on automatic. When the house works again, put that laptop back on Automatic so it follows the router.

Step 4: wake or fix the computer

Power light. Fan. Screen if it has one. Asleep or dark? Start with is the computer still on?. Soft-off on purpose? Wake the computer from the house network. Old laptop that sleeps with the lid? Don't let the laptop sleep.

When it answers, SSH in: SSH from the couch. Connect fails? when SSH won't connect. Then:

pihole status

You want FTL running. If not:

sudo systemctl restart pihole-FTL

Open the admin page at http://pi.hole/admin or the computer's address plus /admin. Blank or timed out? When the Pi-hole admin page won't open. Admin opens but totals stay at zero after you re-point DNS later? When Pi-hole shows no queries.

Confirm the computer still has one stable house address: find it on the house network. Two addresses fighting? When the old PC has two house addresses.

Step 5: point the house at Pi-hole again

Only after pihole status looks healthy and you can open the admin page from a laptop on house Wi-Fi. Set LAN / DHCP DNS primary to the computer's address again: point common home routers at Pi-hole. Save. Renew leases on phones.

Browse a site that used to show ads. Sites should load. A lot of banners should not. Query log should move. If ads stay gone nowhere, walk when ads come back. Keep the number from drifting: keep the computer on the same address on common routers.

What this is not

This is not a factory reset of the router on night one (that wipes Wi-Fi passwords and reservations). It is not a new mesh kit, a Raspberry Pi, or opening Pi-hole to the internet. It is not “ads came back while sites still load” — that checklist is when ads come back. It is not one blocked bank domain — that is when a site won't load after Pi-hole.

What next

Leave DNS on the computer once the house is calm again. After the next reboot, glance at the three house jobs: after a reboot, check the computer still does its jobs. Tired of typing the number? Add a local name in Pi-hole. Tabs sticky but sites eventually load? When browsing feels slow after Pi-hole. Save settings before you experiment: save a Pi-hole backup.

Optional: jot that you put DNS back / re-pointed after a browse outage in Lab plan — username + passkey, no email. Skip if you just want to keep reading.

Skip

• Skip a factory reset of the router because names timed out once.
• Skip a mesh kit, a new gateway, or a Raspberry Pi for this outage.
• Skip opening Pi-hole (or SSH) to the public internet.
• Skip leaving the whole house on 1.1.1.1 forever if you still want house-wide ad block.
• Skip this if sites load and only ads came back. That is a different walk.
• Skip this if only one site is broken. Allow that domain instead.