Block ads on every device in your home, from your PC

• AdHole runs on Windows (64-bit) and on Linux with systemd. Install it on a PC at home and that PC becomes the DNS filter.
• On that PC it goes further than a DNS filter can: it removes YouTube video ads and rejects cookie banners in its browsers.
• The trade-off: the PC must stay on for the devices that go through it. If you’d rather not leave one on, the same program runs on a Raspberry Pi 4 or 5. AdHole on Linux and Raspberry Pi

1. 01

   Find this PC’s address.

   The dashboard shows it as “this computer’s address”, and adhole status prints it too.

2. 02

   Reserve it in your router.

   In your router’s settings, reserve this address for the PC, so it never changes. It’s often called a DHCP reservation or a static lease; the menu names vary by router.

3. 03

   On Windows, set the network to Private.

   Otherwise the firewall keeps your devices out. Settings → Network & internet → Wi-Fi or Ethernet → your network → Network profile type → Private network.

4. 04

   Set each device’s DNS to that address.

   In the device’s network settings. Samsung and LG TVs, Android TV and Google TV, PS5, Xbox, iPhone, Android: the step-by-step guide.

5. 05

   Check it in the dashboard.

   Use the device for a minute: its requests show up in the dashboard, blocked ones included. If nothing shows up, the device is still asking your router, often through IPv6: see below.

The usual advice is to hand out your PC as the DNS server from your router, for every device at once. We tried it on a Bbox, a router from the French provider Bouygues Telecom, on 12 September 2026. It didn’t work, for two reasons.

The router added the PC, it didn’t replace itself

Its own address stayed as the first DNS, locked, and the PC came second. A device asks the first server that answers, and the router always answers: the filter would almost never be asked, while looking set up.

The router announces its own DNS over IPv6

Devices prefer IPv6, and nothing in that router’s interface changes the announcement. Even a correct DNS setting in IPv4 would be bypassed.

Your router may behave differently: the dashboard tells you, since a device that uses AdHole shows up there. What gets around both traps is the DNS entered on each device. To cover the whole home without touching each one, you need a router you control, such as one running OpenWrt, behind your provider’s: it can hand out a single DNS and stop the IPv6 announcement.

• Devices pointed at this PC lose internet access when it’s off or asleep, or while AdHole is stopped. That’s the real cost of this method.
• Updates install at night, between 3 and 5 a.m.: filtering pauses while one installs (the terms of use allow for about thirty seconds), and those devices have no DNS meanwhile.
• If AdHole crashes, it restarts on its own: in 1 s on Windows, 5 s on Linux.
• This PC keeps your router behind AdHole as a fallback. The devices you pointed at it only have the address you gave them.
• To undo it on a device, set its DNS back to automatic.

The filter answers local addresses only: private networks such as 192.168.x.x and 10.x.x.x, link-local addresses, and the shared 100.64.0.0/10 range. Any other address gets a refusal, so AdHole never becomes an open resolver on the internet.

On Windows, the firewall opens its ports to the local network only, on private and domain networks. On Linux, the ufw or firewalld rules open port 53 to your local network only.