How to Fix Wrong DNS Settings Causing Random Site Failures
Some websites won't load while others work fine - incorrect DNS settings are likely the culprit, and here's how to fix them.
What's Happening
Some sites load instantly, others hang forever or throw "DNS server not responding." The internet itself is clearly working, which is what makes this so confusing. DNS is the phone book that turns a name like example.com into an IP address. When it's broken, the request to find the address fails before any connection is even attempted — so the site that does work and the site that doesn't are failing for the same reason: a flaky or poisoned resolver, not the websites. The pattern of which sites fail tells you where the bad lookup is happening.
Quick Checks (Do These First)
- Can you reach a site by raw IP? Type
http://1.1.1.1in a browser. If that loads but names don't, it's DNS, full stop. - Flush the local cache.
ipconfig /flushdns(Windows) orsudo dscacheutil -flushcache(Mac). - One device or all of them? All devices = the router's DNS. One device = that device's DNS or cache.
- Same sites failing every time, or random? Consistent failures point to a specific bad resolver entry; random failures point to an overloaded or failing DNS server.
The Test That Names the Culprit Exactly
Don't change settings blindly — find out which resolver is lying. Open Command Prompt and run two targeted queries:
nslookup example.com— uses whatever DNS your device is currently set to. If this fails or times out, your current resolver (router or ISP) is the problem.nslookup example.com 1.1.1.1— forces the query through Cloudflare directly. If this succeeds while the first failed, the websites are fine and a public DNS switch will fix everything. If this also fails, the lookup is being intercepted or blocked before it leaves your network — think captive-portal hardware, a security appliance, or DNS hijacking malware.
One pair of commands tells you whether to change DNS, scan for malware, or look at the hardware in front of you. Content-farm guides skip this and just tell everyone to change DNS, which only works for the first case.
Step-by-Step Fixes
Fix 1: Change Router DNS to a Reliable Public Resolver (Most Effective)
- Log into the router (
192.168.1.1or192.168.0.1) - Open Internet / WAN Settings and find DNS Servers
- Switch from "Get from ISP" to Manual
- Cloudflare:
1.1.1.1/1.0.0.1, or Google:8.8.8.8/8.8.4.4 - Save, reboot the router, wait two minutes, retest the sites that failed
This replaces the ISP resolver for every device at once — the right move when the problem hits all devices.
Fix 2: Set Static DNS on One Device (Quick Test or Single-Device Fix)
Windows: Settings > Network & Internet > Wi-Fi > Hardware properties > Edit next to DNS server assignment > Manual > IPv4 on > Preferred 1.1.1.1, Alternate 8.8.8.8 > Save.
Mac: System Settings > Network > your connection > Details > DNS > add 1.1.1.1 and 8.8.8.8, remove the others > OK.
Fix 3: Clear the Router's DNS Cache
- In the router admin, look for a Clear DNS Cache or Flush DNS option in advanced settings
- No such option? Just power-cycle the router — unplug 30 seconds, plug back in, wait for full boot
- Retest the problem sites
Fix 4: Disable IPv6 as a Test
- In router settings, find IPv6 and disable it
- Save and reboot
- If sites that resolved over a broken IPv6 path now work, leave it off; otherwise turn it back on
Where DIY Stops — And Why
If nslookup example.com 1.1.1.1 still fails after a router reboot, the lookup is being broken before it ever reaches the public internet — and a settings change can't reach that. Past this point it's usually one of these:
- DNS hijacking malware on a device or in router firmware quietly rewrites every lookup to point somewhere malicious. New public DNS settings get silently overridden, which is why "change DNS" appears to do nothing.
- Compromised or buggy router firmware intercepting and mangling DNS, sometimes only for certain domains — the classic "some sites, not others" pattern that survives every settings change.
- An upstream block at the ISP or line level where queries to outside resolvers are filtered or the connection is too lossy for DNS to complete reliably.
Telling malicious DNS interception apart from a failing router or an upstream block means inspecting actual query traffic, not router menus — and that's the boundary where a network repair and security check is worth more than another round of settings changes, especially if banking or work data is on the line.
Need Professional Help?
If you're in the Tampa Bay area and dealing with persistent internet connectivity issues, Geeks in Sneaks provides friendly, on-site tech support in Clearwater, Clearwater Beach, and Dunedin.
Related Topics
Need Professional Help?
If you're still having trouble, our expert technicians can help.
Learn about our network repair serviceMore Router & WiFi Fixes
See all Router & WiFi fixes →Business-Grade vs Consumer Routers for Home Use
Considering a business-grade router for your home? Find out if the premium price delivers real benefits for residential use.
Buying Used or Refurbished Routers: Safe or Risky?
Tempted to save money with a used router? Learn the real security risks and when buying secondhand is safe versus when it's dangerous.
How Long Should a Router Last? When to Replace Yours
Your router is a few years old and you're wondering if it's time to replace it. Learn the typical lifespan and warning signs it's failing.
Gaming Routers: Real Benefits vs Marketing Hype
Wondering if a gaming router is worth the premium price? We separate the real performance benefits from marketing gimmicks.
Renting ISP Equipment vs Buying Your Own: Real Cost Comparison
Paying monthly rental fees for your modem and router? Find out how much you could save by buying your own equipment.
Matching Router Capabilities to Your Internet Speed Tier
Have gigabit internet but not getting those speeds? Your router might be the bottleneck. Learn how to match equipment to your plan.
What to Look for When Buying a Home Router in 2026
Shopping for a new router can be overwhelming with all the technical specs and marketing claims—here's what actually matters in 2026.
When to Move from Single Router to Mesh WiFi System
Dead zones and weak WiFi in parts of your home? Find out if it's time to upgrade from a traditional router to a mesh system.