Infographic showing Windows 11 DNS requests routed through AdGuard Home and Unbound for local filtering and privacy.
MakeUseOf's Afam Onyimadu describes a way to stop any single DNS company from holding your full browsing lookup history. It is a local resolver chain on a Windows 11 PC. It isn't magic, and "nobody" doesn't mean what the headline suggests. Below is what the setup does, how to check it, and what it leaves exposed.

Infographic showing Windows 11 DNS requests routed through AdGuard Home and Unbound for local filtering and privacy. The chain: Windows, AdGuard Home, Unbound, then the DNS hierarchy​

Both tools want port 53, so Onyimadu configured Unbound to listen on port 5335. AdGuard Home keeps port 53 and receives DNS requests from Windows. The flow is:

  1. Windows asks AdGuard Home. It filters the query and records it in a readable log.
  2. AdGuard Home passes anything it can't answer itself to Unbound at 127.0.0.1:5335.
  3. Unbound walks the DNS hierarchy itself. It asks the root servers, then the TLD servers (such as .com), then the domain's authoritative server, and caches the answer.

NLnet Labs describes Unbound as a validating, recursive, caching resolver. Its documentation lists Microsoft Windows among the supported platforms.

AdGuard Home's own documentation covers the Windows side. From an elevated Command Prompt, running AdGuardHome.exe -s install registers it as a Windows service. The first-run wizard listens on port 3000, and the DNS server uses port 53. That is why no terminal window has to stay open.

Other people run the same pairing. Independent guides for Linux and router setups also use 127.0.0.1:5335 as the sole upstream, so the pattern is common. The MakeUseOf piece is the Windows desktop version of it.

Setting it up and checking it​

The upstream field decides whether any of this is private:

  • In AdGuard Home, go to Settings > DNS settings > Upstream DNS servers.
  • Remove the existing entries. Onyimadu says out of the box AdGuard Home points at Quad9. That is his account of a fresh install, so check your own field rather than assuming.
  • Enter 127.0.0.1:5335 and click Test upstreams.
  • Open Unbound's configuration and look for forward-zone or forward-addr entries. Unbound's manual says a forward zone makes Unbound hand the query to a remote recursive server instead of recursing itself. A forward entry to Quad9 or Mullvad would quietly undo the point of the exercise.
  • Visit a site you've never used and confirm it shows up in AdGuard Home's query log.
  • Run a DNS leak test. Onyimadu says it should name your ISP as the resolver.

AdGuard's FAQ adds a quick check from Command Prompt. Run nslookup example.org and confirm the server address shown is the one where AdGuard Home runs.

Treat the leak test as a clue, not proof. It reflects one test at one moment. It can't show that every application is using your resolver.

Common ways it gets bypassed​

  • A second network adapter with an old DNS address. Onyimadu says this can leave queries going elsewhere. Check every active adapter, not only the one you edited. AdGuard's guide walks through the manual route: Control Panel, Network and Sharing Center, Change adapter settings, then the IPv4 or IPv6 properties.
  • Browser encrypted DNS. Onyimadu says Firefox can skip your setup if you turn on encrypted DNS in the browser. Browsers with their own DNS-over-HTTPS setting can do the same. Windows 11 also supports encrypted DNS, per Microsoft's security documentation, so review that setting too.
  • Port conflicts. Because both services default to port 53, the separate Unbound port is what keeps them from colliding.

Reading the query log without breaking Windows​

The most useful part of the piece is a warning. Onyimadu says dns.msftncsi.com was the first entry that caught his eye. It is part of Windows' online check, and blocking it can make Windows think you're offline.

Microsoft's NCSI documentation backs this up. The DNS probe goes to dns.msftncsi.com, and the web probe goes to [www.msftconnecttest.com/connecttest.txt](http://www.msftconnecttest.com/connecttest.txt). Microsoft says that starting in Windows 11, HTTP is always used for the active probe. Even so, a DNS lookup is still needed to find where to send it. Microsoft also lists DNS resolution problems for the NCSI lookup names among the things that can make a probe fail.

On Windows 11, a dns.msftncsi.com entry in your log is therefore normal. If you block the NCSI names, expect a "no internet" taskbar icon while websites still load. Microsoft's FAQ says Office and the taskbar icon both rely on NCSI.

Onyimadu sorted his log into four groups. These are his observations, not universal rules:

SourceExamplePattern he sawHis blocking advice
Windows connectivity checksdns.msftncsi.comSteady all dayDon't block
Windows telemetryvortex.data.microsoft.comBursts, even when idleUsually, but test first
Background appsclients3.google.comSpread through the dayDepends on the app
Ads and trackersdoubleclick.netSpikes while browsingBlock

A DNS log only shows which domains software asked about. It doesn't show what data was sent afterward. He suggests running AdGuard Home's default filter list for at least a week before adding custom rules. That way, when something breaks, you know which block caused it.

What "nobody" really means​

The headline overstates it. Onyimadu's own conclusion is narrower: no single company gets the full list. Here is who sees what:

  • Your ISP can see DNS queries leaving your PC and the IP addresses you connect to. This is not a VPN replacement.
  • Root and TLD servers see only part of the name when QNAME minimization is on. Unbound's manual calls this best effort. It can send the full name and original query type in some error cases.
  • Authoritative servers see queries for their own domains coming from your home IP address.
  • Anyone with access to your PC can read the AdGuard Home log. You can set retention limits or turn logging off. AdGuard's configuration documentation lists these log controls.

You haven't hidden your lookups. You've spread them across several parties instead of handing them all to one. If your threat model is "I don't want Google or Cloudflare to hold my complete history," that is a real improvement. If it is "my ISP shouldn't know where I go," this doesn't solve that.

Trade-offs​

  • Speed. Onyimadu says rarely visited sites loaded slightly slower because Unbound follows the full recursion path. That is his impression, not a benchmark. Caching should make repeat lookups quicker.
  • Setup time. He says setup took about four minutes. Plan on longer if you also need to find stale adapter settings or browser DNS options.
  • Scope. By default the setup covers only the PC. You can point other devices at it, but then it needs to stay reachable.
  • Public resolvers still have a role. Some people prefer an encrypted public resolver for the ISP-facing privacy it provides. Recursive resolution trades that for spreading lookups across more parties. Which is better depends on whom you trust less.

Verdict​

This is a practical, fairly low-effort Windows 11 privacy project, and AdGuard Home and Unbound both document Windows support. The failure points are quiet: a leftover Quad9 upstream, a forwarding entry in Unbound, a stale adapter, or a browser with its own encrypted DNS. Check each of them, and don't block the Windows connectivity probes just because the log is full of unfamiliar names.

 

References

  1. My DNS provider sees every site I visit, so I built a setup where nobody does MakeUseOf 2026-11-21T14:30:16+00:00
  2. Documentation for Unbound by NLnet Labs unbound.docs.nlnetlabs.nl
  3. unbound.conf(5) - Documentation for Unbound by NLnet Labs unbound.docs.nlnetlabs.nl