Your DNS is configured in four places, and they're all wrong

Your DNS is configured in four places, and they’re all wrong — here is a clear breakdown of what happened and why it matters right now.

The details below put the news in context: the key points first, the background after.

Here’s a fun fact that nobody tells you when you set up your home network: your laptop, your phone, your router, and even your web browser can all be using completely different DNS servers at the same time, and none of them are talking to each other about it. You might think you’ve got one tidy address book for the whole house, but you actually have four, and they disagree.

This drove me up the wall when a buddy called me because “the internet is broken” on his PC, but fine on his phone. Same Wi-Fi, same room, totally different behavior. The culprit wasn’t his ISP or his router. It was DNS being configured in multiple different places, with every layer overriding the one below it.

Here’s a quick refresher so we’re on the same page: DNS is the system that turns a name you can read, like google.com, into the numeric IP address your devices actually need to connect. Every single time you load a page, this lookup happens first, before anything else.

That lookup can be slow or broken even when your actual connection speed is blazing fast, because DNS happens before the website loads at all.

So you run a speed test, it says 900 Mbps, and you stand there confused because pages still take forever to pop up. That’s DNS being the bottleneck, not your bandwidth. And to make things messier, every device keeps its own cached copy of those lookups, with a built-in timer (the TTL) that decides how long the stale info hangs around before it refreshes.

From 8.8.8.8 to how your browser finds cat videos — find out how much you really know about DNS.

Before DNS was invented, how did computers resolve hostnames on the early internet (ARPANET)?

The famous DNS server at IP address 8.8.8.8 is operated by which company?

Cloudflare’s DNS resolver at 1.1.1.1 launched in 2018 with a strong emphasis on what selling point?

What is a DNS ‘resolver’ (also called a recursive resolver)?

What type of attack involves poisoning a DNS cache with false records to redirect users to malicious websites?

Which DNS record type is responsible for mapping a domain name to an IPv4 address?

DNS-over-HTTPS (DoH) and DNS-over-TLS (DoT) both aim to solve the same core problem. What is it?

What used to be a one-step setting has turned into a three-way fight between your browser, your operating system, and your router. Toss your phone into the mix, and you’ve got four contestants.

Your router hands out DNS servers to every device through DHCP. Your operating system, like Windows, can override those router settings with its own configuration. And your browser can use encrypted DNS, called DNS-over-HTTPS, that bypasses both the router and the OS entirely. The hierarchy shakes out like this: browser settings beat OS settings, which beat router settings. If all three are set differently, the browser wins for browser traffic, the OS wins for system traffic, and the router only wins for the devices that don’t have their own DNS opinion, like most of your smart-home junk.

So you might think you’ve locked down your whole network with a nice privacy-focused DNS provider, while Chrome is sneakily routing its traffic through Google’s servers instead, and Windows is ignoring your router completely. The browser even does this on its own. Chrome’s Secure DNS is on by default in a lot of regions, and Firefox’s DNS-over-HTTPS can override both your system and your router setup.

A good router won’t fix DNS issues, but it can be the foundation of a great network. UniFi’s Dream Router 7 is one such “good router.”

People treat a DNS problem as if it has one source. They flush the cache on the PC, it seems fixed for a day or two, then it breaks again because the browser’s Secure DNS or the router’s DHCP setting was never touched.

You absolutely can change DNS in each spot. On Windows 11, you head into Settings, then Network & Internet, pick your network, and switch the DNS assignment from Automatic to Manual to punch in something like Cloudflare’s 1.1.1.1. On iPhone, you tap the little (i) next to your Wi-Fi network and set Configure DNS to Manual. On Android 9 and up, the Private DNS setting is its own beast that applies to every network, Wi-Fi, and cellular alike, using DNS-over-TLS.

See the problem? Four separate places, each with its own quirks, and any one of them can become the layer that might sabotage you later. Fixing them piecemeal is how you end up troubleshooting the same “bug” for a week.

The fix for this whole mess of problems is refreshingly straightforward once you stop playing whack-a-mole. The goal is to get every layer pointed at the same DNS provider so there’s nothing left to disagree about.

Start by picking your provider, like Cloudflare’s 1.1.1.1, Google’s 8.8.8.8, or Quad9 at 9.9.9.9. Then configure it at the router level first, because that’s the setting that blankets every device on your network at once. To do it, log into your router’s admin page and dig for the DNS setting under WAN, Internet, or DHCP.

Next, go check your Windows network adapter and rip out any manual DNS entries that are overriding the router, then either disable the browser’s Secure DNS or set it to that same provider so it stops doing its own thing. Heads up, though: some locked-down ISP routers won’t let you change DNS at all, and in that case, you just have to set it on each device individually instead. Annoying, but at least now you know to hit every device on purpose.

Even after you change DNS servers, your devices will still be holding onto their old cached lookups, so you need to flush the cache to force them to grab fresh info.

On Windows, that’s just popping open Command Prompt or PowerShell and running ipconfig /flushdns. For the router and your other gear, powering everything down for a few minutes and restarting it will make them boot back up with a clean slate. Do this everywhere you just changed a setting to make sure the fix sticks.

If there’s one thing to remember here, it’s that DNS isn’t a single switch you flip in one place. It’s as many as four separate switches scattered across your router, your OS, your browser, and your phone, and they will absolutely give you different answers if you let them. That’s the entire reason “it works on my phone but not my PC” exists as a phenomenon. Pick one provider, set it everywhere, flush the old cache, and suddenly all the weird intermittent nonsense that you blamed on your ISP will disappear.

Network issues? My first step is always to go wired with a cable I can trust, which is why I keep recommending these Ugreen cables.