How to Fix a Website That Won’t Open Due to DNS Pollution

One website suddenly refuses to load. Every other site works fine, and this one worked yesterday. You changed nothing, so what happened?

In most cases, DNS pollution

is the cause. This guide shows you how to confirm a website won’t open due to DNS pollution and fix it step by step. DNS poisoning is common, and it is almost always temporary.

The fixes range from a one-minute DNS change to advanced options, including routing your traffic through a US server to bypass local DNS issues. DNS poisoning rarely survives a server switch. Start with the simplest method, and stop as soon as the website loads again.

You do not need technical skills. Test the website after each change. Most people restore the website within minutes.

Key Takeaways

• DNS pollution happens when your device gets a wrong address for a website, so the site won’t load.
• Quick fixes include restarting your router and switching to a public DNS server like 8.8.8.8.
• A VPN or secure DNS can bypass the problem temporarily while you fix it.
• Flushing your DNS cache and editing the hosts file can solve stubborn cases.
• If nothing works, contact your ISP or the website owner with details about the error.

DNS Poisoning Explained Simply

How Normal DNS Lookup Works

Every time you type a website address, your device asks a DNS resolver for the site’s numeric address. This process is called DNS resolution. A normal lookup is fast. Most requests finish in 20–120 ms on a responsive connection. Delays become noticeable at 150 ms and above, and anything over 200 ms deserves a closer look.

Your device stores recent answers in a DNS cache. This cache saves time on repeat visits. A correct answer points your browser to the real server. A tampered answer points it somewhere else, or nowhere at all. DNS poisoning breaks that trust. A slow answer feels like a broken website, but the lookup itself is not the problem.

What DNS Cache Poisoning Does

DNS cache poisoning replaces a correct answer with a false one. Someone inserts a bogus record into the DNS cache, and your device trusts it. This trick is also called DNS cache spoofing. The result is simple: your browser goes to the wrong place, and the website fails to open. This kind of DNS cache poisoning is the likely culprit here.

DNS poisoning can target one device or a whole network. That explains why some sites fail while others load fine. A single bad record in the DNS cache affects only the sites it covers. Other lookups still return correct answers. DNS poisoning never touches every website at once.

A DNS poisoning attack often starts with a weak router. Repeated DNS attacks point to an unpatched device on your network. DNS poisoning spreads through that gap. You can spot DNS poisoning when one website fails and others work. DNS poisoning leaves the rest of your browsing intact. DNS cache poisoning is temporary. Most DNS poisoning cases clear up fast. Fixing DNS poisoning starts with the steps below.

Confirm a Website Won’t Open Due to DNS Pollution

Quick Checks on Your Device

Start with a few fast tests. Open the same website on a different device on your network. Then try a different browser, and open an incognito window. A hard refresh helps too: press Ctrl+Shift+R on Windows, or Command+Shift+R on Mac. These steps show whether the problem lives in one browser or across your whole network.

Next, rule out interference. Turn off your VPN and antivirus software for a minute, then reload the page. Check your firewall settings as well. A strict firewall rule can block a site and mimic a DNS fault. If the website loads with the VPN off, the VPN is the culprit, not DNS poisoning.

Signs That Point to DNS Issues

Watch for a clear pattern. Some websites fail while others load normally. That pattern suggests DNS resolution is being tampered with, and it is the strongest hint that you face DNS poisoning. You can also detect DNS poisoning through error messages. A “DNS server not responding” message or a “domain could not be found” error points straight at DNS.

Other signals help you detect DNS poisoning. Unexpected redirects, certificate warnings, and slow first loads all fit the profile. A mismatch between the URL and the page content is another red flag. Run nslookup or dig and compare the returned address with the expected one. An odd result confirms tampering.

Enable DNSSEC to protect against tampering; use DNS-over-HTTPS (DoH) or DNS-over-TLS (DoT) for encrypted lookups; run periodic malware scans to prevent host file modifications; keep routers and firmware updated to reduce DNS hijacking risks.

Sign	What It Indicates
Unexpected Redirects	A familiar URL lands on a different site or an odd login prompt
Browser Security Warnings	“Certificate not trusted” messages suggest an impostor site
Incorrect IP Address Resolution	nslookup or dig returns an unexpected address
Unauthorized DNS Changes	Device or router DNS settings changed without your knowledge

These checks take a few minutes. They give you solid ground for the DNS troubleshooting steps ahead.

Fast Fixes to Fix DNS Poisoning

Restart and Switch DNS Servers

Begin with the basics. Restart your router and modem, then reboot your device. This clears many temporary faults. Next, release and renew your IP address so your device asks for a fresh lease. These steps cost nothing and often end the problem.

If the site still fails, change your DNS server. Google’s public resolver at 8.8.8.8 is a solid first choice, with 8.8.4.4 as the backup. Here is where to find the DNS settings on each platform:

1. Windows 11: Open Settings > Network & Internet > Advanced network settings, select your connection, choose View additional properties, click Edit for DNS server assignment, switch Automatic (DHCP) to Manual, enable IPv4, enter 8.8.8.8 and 8.8.4.4, then Save.
2. Windows 10: Open Settings > Network & Internet > Change adapter options, right-click the connection, select Properties, choose Internet Protocol Version 4 (TCP/IPv4), click Properties, pick Use the following DNS server addresses, enter 8.8.8.8 and 8.8.4.4, then click OK.
3. Mac: Open System Settings > Network, select Wi-Fi or Ethernet, click Details, select DNS, click the plus button, add 8.8.8.8, then add 8.8.4.4, and click OK.
4. Router: Sign into the firmware, find the internet or network DNS section, switch from automatic to manual assignment, enter 8.8.8.8 and 8.8.4.4, and apply.

Testing with 8.8.8.8 also tells you whether an internal DNS proxy or filter causes the fault. If the site loads on the public resolver but fails on your old one, a local filter is the culprit.

Why does this work? Google Public DNS validates DNSSEC signatures and rejects any response whose signature does not match, which blocks injected fake addresses. It also returns genuine NXDOMAIN answers instead of hijacking errors, and it keeps a fresh global cache.

Wilmer van der Gaast recounts that the Dan Kaminsky cache-poisoning disclosure showed 16 bits of entropy was insufficient and that services not randomizing port numbers were highly susceptible to cache poisoning.

That history explains why a trustworthy resolver matters. A poisoned or filtered DNS server hands back false answers, and switching away restores authentic resolution.

Use a VPN or Secure DNS

A VPN or secure DNS bypasses the polluted result. DNS over HTTPS wraps queries inside encrypted HTTPS connections, so third parties on the network path cannot intercept or manipulate them. This shielding stops DNS injection attacks and blocks malicious redirections. Treat it as a temporary workaround when you need the site now.

VPN protection varies by provider. ExpressVPN, NordVPN, Surfshark, IPVanish, and ProtonVPN resist DNS session inference through special DNS handling. PIA, PrivateVPN, CyberGhost, and Windscribe showed vulnerability in testing. Choose a protected provider if you rely on a VPN.

Finally, update your router firmware. Fresh firmware patches known flaws and reduces recurring DNS errors. A quick check for updates takes a minute and prevents repeat trouble.

Advanced Fixes for Stubborn Cases

Flush Your DNS Cache

A stale or corrupted DNS cache keeps serving the bad answer even after you switch DNS settings. Flush your DNS cache to force a fresh lookup. On Windows, open Command Prompt as administrator and run ipconfig /flushdns. On Mac, the command depends on your version.

Chrome keeps its own DNS resolver cache. Clear DNS cache there too, then reset Chrome’s network settings under Settings > Reset settings. On Windows, restart the DNS Client Service as an extra step: open Services, find DNS Client, and choose Restart. This step clears the dns cache at the service level and stops dns poisoning from lingering.

Edit the Hosts File and Reset Network Settings

The hosts file overrides DNS answers on your device. Editing it lets you point the website at its correct address. Open the file as administrator: C:\Windows\System32\drivers\etc\hosts on Windows, or /etc/hosts on Mac. Add one line with the correct IP address, a space, and the domain name.

Back up the hosts file before you edit it, and remove the entry once the site loads again. A forgotten entry causes new problems later.

Reset network settings if the trouble persists. On Windows, open Settings > Network & Internet > Advanced network settings > Network reset. On Mac, remove and re-add your network service. These steps clear leftover dns settings and rebuild the connection. A persistent dns server not responding error after all this points to a wider dns poisoning issue upstream.

When to Contact Your ISP or Site Owner

What to Report and Expect

Escalate once your own fixes fail. A network-wide failure points to your ISP. Test the website on two devices on the same network. Then test it on mobile data. If the website fails on every device behind your router but loads on cellular, your ISP or router is the likely source. If the website fails everywhere, the site owner may face dns attacks or an outage.

Gather details before you call. Note the site URL, the exact error message, and the times the failure occurs. List the devices you tested and the dns settings you tried. Mention any dns server not responding message. Report whether other websites load fine and whether this website fails alone. This evidence helps support staff spot a dns server issue fast.

Expect variable response times. ISPs handle reports at different speeds, and some resolve dns poisoning within hours. Others take days. Keep your workaround active while you wait. A VPN or secure dns keeps the website reachable in the meantime. If the site owner confirms dns attacks, the fix sits on their side.

Document each contact. Follow up if the dns poisoning persists beyond the promised window. Persistent dns poisoning on your line may need a firmware update or a new router. Ask your ISP whether it filters dns traffic. Some providers run transparent dns proxies that reintroduce the fault, and the website stays blocked until you opt out.

A second dns server not responding error after a fresh restart strengthens your case. Tell the agent you already flushed your dns cache and switched to a public dns server. Mention the exact dns settings you used. That detail moves your ticket past basic troubleshooting.

Repeat the check on a second website you trust. A pattern of failures on many websites suggests broad dns poisoning rather than one bad record. Ask whether the dns resolver on your line is healthy. Broad dns poisoning often traces back to your router, and your ISP can confirm it.

Keep a written log of every dns poisoning symptom. Note the date, the time, and the website that failed. If the dns poisoning returns after each fix, ask for a line test. A technician can check for dns poisoning on the local loop. Request a dns log review.

Set a realistic deadline of one business day for a first reply. Use the waiting time to confirm the website works through your VPN. If the website loads there, you have a solid workaround until the ticket closes. Keep your alternate dns ready.

Follow the fixes in order. Restart your router and modem first, then switch to public DNS servers like 8.8.8.8. Try a VPN or secure DNS next. Flush the cache and edit the hosts file last. Most DNS poisoning cases clear within minutes.

Prevent DNS poisoning with simple habits. Enable DNS over HTTPS to prevent DNS poisoning on public networks. Keep a trusted secondary resolver to prevent DNS poisoning when one fails. Update router firmware to prevent DNS poisoning at the source.

A website that won’t open due to DNS pollution is not a broken device. This website issue is temporary, and you can fix DNS poisoning fast.

FAQ

How do I know the problem is DNS poisoning and not a site outage?

Test the same website on another device and on mobile data. If it fails only behind your router, suspect dns poisoning. A real outage fails everywhere. Also check the dns server address your device reports.

Will switching to 8.8.8.8 always fix DNS poisoning?

Not always. A public resolver like 8.8.8.8 bypasses a tampered local dns server, and that clears most cases of dns poisoning. If the site still fails, the fault sits upstream or in your dns cache.

Does a VPN stop DNS poisoning for good?

No. A VPN or dns over HTTPS hides your queries from the local network and sidesteps dns poisoning while it runs. Turn it off and the old dns path returns. Treat it as a workaround, not a cure.

Why does DNS poisoning come back after I fix it?

A stale dns cache or an unpatched router keeps feeding bad answers. Flush the cache, update router firmware, and confirm your dns resolver. Repeat dns poisoning often traces back to one device on your network.

Can DNS poisoning affect my whole home network?

Yes. One poisoned router serves every device behind it, so dns poisoning can block a website for the whole household. Test on mobile data first. Then change the dns settings at the router level and restart the dns client service.