PC Privacy Software All articles
Home Network Privacy

The Month My ISP's DNS Log Went Quiet—and What Still Leaked at the Router

PC Privacy Software
The Month My ISP's DNS Log Went Quiet—and What Still Leaked at the Router

Photo: John Phelan, CC BY 4.0, via Wikimedia Commons

For 30 days, I ran a small experiment in my own house: one Windows 11 desktop, one Windows 11 laptop, a handful of phones, a smart TV, and a router that logs more than most people realize. The goal was not to disappear from my ISP. It was to answer a narrower question: if I switch the house to encrypted DNS, what does the ISP's view actually lose?

I kept a baseline week on the ISP's default DNS, then moved the PCs and router to DNS over HTTPS, usually shortened to DoH. I pulled router logs, checked Windows network settings, and repeated the same browsing routines. This is not a lab test. It is a real household with streaming, schoolwork, and too many browser tabs. But the before-and-after difference was clear enough to be useful.

At PC Privacy Software, we test privacy tools on real PCs, and this one is a good example of a setting that helps in a specific way without being magic. Encrypted DNS is worth doing. It is also easy to overrate.

The setup: boring on purpose

I did not install a new firewall, a VPN, or a custom router firmware. I wanted a setup a normal Windows 11 user could copy in about 20 minutes.

On the Windows 11 machines, I went to Settings > Network & internet > Wi-Fi or Ethernet > Hardware properties > DNS server assignment. I set manual IPv4 DNS to a public resolver that supports DoH, then chose Encrypted only (DNS over HTTPS) for the DNS encryption setting. Cloudflare and Quad9 both work here. NextDNS is another option if you want filtering and a dashboard, though its free tier has limits.

On the router, I enabled the built-in encrypted DNS or DNS-over-HTTPS upstream option. Not every router has this. If yours does not, the Windows settings still cover the PCs, but phones, consoles, and smart TVs may keep using the router's plain DNS. That gap matters, and it shows up later in this story.

I also turned on router logging for DNS and outbound connections. I am not naming my ISP because the point is not the brand. The point is the pattern.

Before and after: what the logs actually showed

In the baseline week, my router log was chatty. Every time a device looked up a website, the router recorded a DNS request headed to the ISP's resolver on port 53. I could read domain names in the log. Not every single request, but enough to see the shape of the household: streaming services, school portals, app updates, shopping sites, and a surprising number of connections to analytics domains.

After I moved the Windows PCs to DoH, those readable DNS requests mostly vanished from the router log for those devices. Instead, I saw HTTPS traffic to the encrypted resolver's IP address. The query names were no longer sitting in plain text.

Here is the simplified version of what changed:

What I checked Default ISP DNS Encrypted DNS month
DNS requests to the ISP resolver on port 53 Hundreds per day, readable names Near zero from the configured PCs
Query names in the router log Visible Not visible for DoH traffic
Destination IPs and ports Visible Still visible
TLS server names where sent in the clear Often visible Still visible
Overall traffic volume Baseline About the same

The big caveat: this was not a clean scientific comparison. Streaming habits changed, updates landed, and one family member discovered a new game. But the DNS query names really did stop appearing for the devices I configured.

The two things my ISP could not see

This is the part where encrypted DNS earns its keep. In my logs, two things moved out of plain view.

First, the ISP could not read the DNS question itself. When my PC asked for a domain, that request was encrypted between my machine and the resolver. The ISP could see that I was talking to the resolver, but not the name I typed or the app requested.

Second, the ISP could not read the DNS answer inside that encrypted session. It could not see which IP address the resolver handed back as part of the DNS response. That is a real privacy gain, even if it is narrower than it sounds. The ISP can still watch the next connection I make, and it can often infer a lot from the destination IP and the TLS server name. But the DNS conversation itself was no longer an open book.

That distinction matters. Encrypted DNS hides the lookup, not the visit.

The three places encrypted DNS does nothing for you

1. Destination IPs and TLS server names

Your ISP still sees the IP address your device connects to. In many cases, it also sees the server name in the TLS handshake, known as SNI. Encrypted Client Hello, or ECH, can reduce that exposure when your browser and the site support it, but it is not universal. So even with DoH, a sharp ISP can make educated guesses about where you go.

2. Devices and apps that ignore your settings

This was the loudest lesson at my house. The Windows PCs behaved. The smart TV, a game console, and one work laptop did not always use the encrypted path. Some apps have their own DNS settings. Some devices hardcode a resolver. Some browsers run their own secure DNS and bypass the system setting entirely. If you only fix Windows, you have fixed Windows, not the house.

3. Content, cookies, and your public IP

Encrypted DNS does not encrypt web pages, hide your public IP address, stop tracking cookies, or defeat browser fingerprinting. It does not make unencrypted HTTP safe. It does not stop a website from recognizing you after you log in. It changes one part of the plumbing, and it changes it well, but it is not a cloak.

The 20-minute weekend checklist

If you want to try this yourself, keep it simple. You do not need a spare server or a degree in networking.

  1. Pick a resolver you trust. Cloudflare, Quad9, and NextDNS are common choices. Read the privacy policy before you commit.
  2. On Windows 11, open Settings > Network & internet > Wi-Fi or Ethernet > Hardware properties > DNS server assignment. Set manual IPv4 DNS and choose Encrypted only for DNS over HTTPS.
  3. Check your router for an encrypted DNS or DoH upstream setting. If it has one, enable it and set your chosen resolver.
  4. Look for a router option that prevents fallback to the ISP's DNS. If the router cannot do that, at least set the PCs correctly.
  5. Walk around the house. Check the smart TV, consoles, and any guest devices. Set DNS manually where the device allows it.
  6. Pull your router log after a day. Look for port 53 requests from devices you thought were covered.
  7. Turn on ECH in your browser if it is available. Use HTTPS everywhere you can.
  8. Do not expect encrypted DNS to hide your traffic. Expect it to hide your DNS queries, and judge it on that.

What I am keeping

I am keeping encrypted DNS. The setup was quick, the browsing felt the same, and the router log became noticeably less revealing for the devices I configured. But I am also keeping the caveats. My ISP could still see destinations, timing, and plenty of metadata. The smart TV was a reminder that a household is only as private as its least cooperative gadget.

If you want a privacy project that fits in a weekend, this is a good one. Just go in with the right expectation: encrypted DNS makes your lookups private. It does not make your internet traffic invisible.

All Articles

Related Articles

Nine Router Settings That Quietly Improve Your Home’s Privacy

Nine Router Settings That Quietly Improve Your Home’s Privacy

Five Ad Blockers, One Clean Windows 11 PC, Seven Days: The One I'll Never Install Again

Five Ad Blockers, One Clean Windows 11 PC, Seven Days: The One I'll Never Install Again

Cousin-Proof Your Windows 11 PC: A Holiday Guest Setup That Leaves Your Files Alone

Cousin-Proof Your Windows 11 PC: A Holiday Guest Setup That Leaves Your Files Alone