The pitch is undeniably tempting. Instead of buying a Raspberry Pi or springing for a network-attached storage box, you install free, open-source DNS filtering software on hardware you already own, plug it into your router, and let it stand guard over every phone, tablet, smart TV, and PC in the house. Even better, timing couldn't be sharper: AdGuard just shipped AdGuard Home v1.0.0 on November 19, 2026—a major milestone eight years in the making.
Still, before you dust off an old ThinkPad and declare mission accomplished, an IT reality check is in order. Turning a Windows or Linux laptop into your household's sole DNS gatekeeper comes with real caveats—including one major Windows limitation that can derail router integration, a few quiet Windows power settings that will knock your entire house offline at 2 a.m., and strict limits on which ads DNS filtering can actually erase.
What AdGuard Home Actually Does—and What Slips Right Past It
At its core, AdGuard Home acts as a private DNS sinkhole sitting inside your home network. Whenever a connected device tries to look up a domain name, it asks AdGuard Home first. If that domain matches an enabled ad, tracker, adult-content, or malicious-domain blocklist, AdGuard Home drops the request and returns an empty answer, preventing the asset from ever loading. Clean requests are forwarded upstream to a public resolver—and in the newly released v1.0.0, new installations default to Cloudflare DNS ([url]https://cloudflare-dns.com/dns-query[/url]) rather than Quad9, ahead of Quad9's November 24 geographic restrictions in France.
Because AdGuard Home also inspects DNS responses, it can catch CNAME cloaking—a sneaky tracking trick where a site hides a third-party tracker behind an innocent-looking first-party subdomain—flagging those entries as "Blocked by CNAME or IP" in the query log.
Here is the catch that gets glossed over in "block every ad in your house" headlines: DNS filtering only sees domain names, not the contents inside an encrypted HTTPS webpage or app stream. As AdGuard's own Knowledge Base warns, DNS-level blockers cannot reliably stop ads served from the same domain as the content itself. That list includes some of the biggest offenders on the internet:
- YouTube and Twitch video ads, which share infrastructure and domains with the video streams you actually want to watch.
- Sponsored posts on Facebook, X, and Instagram, which arrive from the same social platform domains as your feed.
- Unknown or brand-new phishing links, because DNS filtering only catches domains already cataloged on active blocklists or flagged by AdGuard's browsing security service—it is a helpful net, not a substitute for endpoint antivirus or browser protections.
Section takeaway: AdGuard Home shines at stripping out third-party ad networks, telemetry from chatty smart TVs and IoT appliances, and known bad domains across devices that can't run browser extensions. Just don't expect it to turn YouTube into an ad-free paradise on its own.
Why AdGuard Home v1.0.0 Makes Old Laptops Even Better—With One Windows Catch
If you have ever looked at AdGuard Home in the past and put it off, November 2026 is a remarkably good week to jump in. Released on November 19 and officially announced the following day, AdGuard Home v1.0.0 replaces the legacy 2018-era dashboard with a rebuilt, responsive web interface that trims memory consumption—welcome news for older laptops with modest RAM—while keeping the exact same AdGuardHome.yaml configuration schema from the v0.107.x branch. (AdGuard also adopted a new versioning model with v1.0, meaning future minor releases like v1.1.0 may introduce breaking changes, so checking release notes before updating is smart.)
Before picking an operating system for that spare laptop, though, you need to check what your home router allows. BGR rightly stresses that the laptop must run an OS that still receives security patches—meaning an ancient Windows 7 machine should either be upgraded to Windows 11 (if supported) or wiped for a lightweight Linux distribution like Ubuntu. On Chromebooks, you either have to work around ChromeOS's DNS port restrictions inside its Linux environment or replace ChromeOS with Linux altogether.
If your old laptop runs Windows 10 or Windows 11, there is one huge architectural wrinkle documented in AdGuard's official wiki: AdGuard Home's built-in DHCP server is not supported on Windows.
Why does that matter? Most households wire AdGuard Home in by logging into their router and typing the laptop's local IP address into the router's LAN DNS settings. Easy enough—unless your ISP-issued router locks down custom DNS fields. AdGuard's docs suggest letting AdGuard Home take over DHCP duties on your network as a workaround when a router won't cooperate. On Linux, that works. On Windows, it doesn't.
| Setup Factor | Windows 10 / 11 Laptop | Linux Laptop (e.g., Ubuntu / Debian) |
|---|---|---|
| Ease of starting | High if Windows is already installed | Requires flashing and installing Linux |
| Background service | Built-in via AdGuardHome.exe -s install | Standard systemd service |
| Built-in DHCP server | Not supported | Fully supported |
| Port 53 conflicts | Usually clear on clean Windows installs | Ubuntu's systemd-resolved occupies port 53 until disabled |
| Update reboots | Monthly Patch Tuesday restarts interrupt DNS | Controlled reboots; lighter background footprint |
Section takeaway: Keep Windows if your router lets you set a custom LAN DNS server—or if you prefer configuring individual devices. Switch the old laptop to Linux if your ISP router hides its DNS settings and you need AdGuard Home to act as your DHCP server.
Hardware Prep: Cable Up and Rethink the "Built-In UPS" Myth
Wireless convenience is great for scrolling on the couch, terrible for infrastructure. If every phone, console, and PC in your house asks that old laptop where google.com lives before loading a page, Wi-Fi latency or packet drops on the server will make your entire internet connection feel broken.
As BGR recommends, park the laptop next to your router and connect it via Ethernet. If your thin-and-light castoff lacks an Ethernet jack, a plug-and-play USB-to-Ethernet adapter solves the problem inexpensively.
And what about the laptop's battery acting as a built-in uninterruptible power supply (UPS), as BGR suggests? Take that with a grain of salt. Yes, a healthy battery keeps the laptop alive during a three-second brownout. On a five-year-old laptop, however, battery cells are often degraded enough to drop from 80% to dead in minutes—or refuse to hold a charge at all. More importantly, unless your modem, router, and ONT are also plugged into a real UPS, a power outage kills your home network immediately anyway. Treat a working battery as a modest bonus, not an enterprise failover plan.
Step-by-Step: Installing AdGuard Home on a Windows Laptop
If you are sticking with Windows 10 or Windows 11, getting AdGuard Home up and running takes about 15 minutes when you follow AdGuard's official Getting Started workflow:
- Reserve a static local IP first. Before touching AdGuard, log into your router's admin panel (commonly
192.168.0.1or192.168.1.1) and create a DHCP reservation for your laptop's Ethernet MAC address. Alternatively, assign a static IP outside your router's DHCP range directly in Windows' adapter settings. If the laptop's local IP changes next Tuesday, your whole house loses DNS. - Download the stable Windows archive. Grab the latest stable release (
AdGuardHome_windows_amd64.zipfor standard 64-bit x86 laptops) from AdGuard's official GitHub Releases page—avoiding beta builds unless you want to test pre-release code. Extract the folder to a permanent home such asC:\Program Files\AdGuardHome. - Allow required ports and firewall access. AdGuard Home uses TCP port 3000 for first-time setup, TCP port 80 for the admin dashboard, and UDP port 53 for plain DNS (plus extra ports if you later enable encrypted DNS-over-HTTPS or DNS-over-TLS). When Windows Defender Firewall prompts you on launch, click Allow access for your private home network.
- Run the initial setup wizard as Administrator. Open Command Prompt or PowerShell as Administrator, navigate (
cd) to your extracted folder, and runAdGuardHome.exe. Open a browser on the laptop and visit[url]http://127.0.0.1:3000[/url]. Follow the wizard, pick your Ethernet interface (rather than binding only to loopback if you want other devices to reach it), and set a strong administrator username and password. - Register it as a Windows service. Close the foreground terminal process (
Ctrl+C), then runAdGuardHome.exe -s installfrom your elevated prompt. This registers AdGuard Home to start automatically with Windows in the background, logging operational events directly to the Windows Event Log. (You can manage it anytime with-s start,-s stop,-s restart,-s status, or-s uninstall.) - Point your router—or individual devices—to the laptop. Open your router's LAN/DHCP settings and enter the laptop's static IP as the primary DNS server. Don't want to touch the router? On another Windows PC, open Control Panel → Network and Internet → Network and Sharing Center → Change adapter settings, right-click your active adapter, choose Properties → Internet Protocol Version 4 (TCP/IPv4) → Properties, select Use the following DNS server addresses, and enter the laptop's IP. (Be aware that per-device Wi-Fi DNS settings on Android and iOS only apply on Wi-Fi, not mobile data.)
Five Quiet Windows Traps That Break Home DNS Servers
Installing the binary is the easy part. Keeping a repurposed Windows laptop reliable 24/7 is where hobbyist setups usually stumble:
- Lid-close and hibernation defaults: By default, closing a laptop lid puts Windows to sleep—instantly severing DNS for your household. Open Control Panel → System and Security → Power Options → Choose what the power buttons do (or Settings → System → Power & battery → Lid & power button controls in Windows 11) and set When I close the lid under Plugged in to Do nothing. Also check Change plan settings → Change advanced power settings → Sleep → Hibernate after so Windows doesn't silently hibernate after a few hours anyway.
- Browser Secure DNS (DoH) bypasses: Modern browsers love shipping their own encrypted DNS settings, which completely ignore your router's DNS advertisement. If ads still flood through Chrome (
chrome://settings/security), Microsoft Edge (edge://settings/privacy), or Firefox (about:preferences#privacy), check and disable their built-in Use secure DNS / DNS over HTTPS toggles so they respect your local resolver. - Hardcoded IoT DNS: Certain streaming sticks and smart home devices hardcode
8.8.8.8instead of honoring DHCP DNS. Without advanced router firewall redirection, those devices simply sidestep your laptop. - The "One-Box" Patch Tuesday problem: If your old laptop is your household's only DNS server, every Windows Update reboot means 60 to 120 seconds where web pages fail to resolve. Schedule active hours carefully—or, if your router lets you specify a secondary DNS server, decide intentionally between redundancy (which lets some ads leak through during reboots) and strict filtering.
- Uninstalling without repointing: If you ever retire the project, change your router and devices back to a working DNS server before running
AdGuardHome.exe -s uninstall. Otherwise, every device still pointing at that laptop's IP will appear "offline" even though your internet connection is fine.
How to Verify Everything Is Actually Working
Never assume a router setting took effect just because you clicked Save. On another Windows PC on the same network, open Command Prompt (cmd.exe) and run:
nslookup example.org
Check the Server: line in the output. It should display the static local IP address of your AdGuard Home laptop. Next, log into AdGuard Home's web dashboard and open the Query Log. You should see example.org appear alongside live lookups from devices around your house.
If the query shows up in the log but unwanted domains aren't getting blocked, head into Settings → General settings to verify Block domains using filters and hosts files is enabled, confirm your lists are active under Filters → DNS blocklists, and check DNS allowlists, DNS rewrites, and Custom filtering rules to ensure nothing is overriding your rules.
Repurposing an old laptop into a network-wide DNS shield won't magically scrub every sponsored video or replace common sense online. Done right, though—with a wired Ethernet link, disabled sleep timers, a reserved IP, and realistic expectations—it turns e-waste into one of the most practical privacy upgrades you can add to a Windows-centric home network.
References
- You Can Use Your Old Laptop To Block Ads On Every Device In Your House - BGR BGR · 2026-11-22T22:47:00+00:00
- Getting started | AdGuard DNS Knowledge Base adguard-dns.io
- microsoft.com support.microsoft.com