 |
| DNS Server Not Responding? How to Fix It While Working From Home |
A "DNS server not responding" error is one of the more confusing messages a computer can show, because it usually appears while your internet connection otherwise looks completely fine. Understanding what DNS actually does makes the fix much more obvious, and most of the time this is a quick, local fix rather than a sign of a real internet outage.
What DNS Actually Does, in Plain Terms
Every website has a numeric address, but nobody types those in — you type a name instead, like a company's internal portal or a public website. DNS is the system that translates the name you type into the numeric address your computer actually needs to connect. When DNS fails, your internet connection itself can be completely fine, but nothing loads, because your computer can't figure out where anything actually is.
This explains a pattern many people find confusing: your video call might work fine (since it often connects using an address already resolved earlier), while trying to open a new website in a browser fails completely.
Step 1: Confirm It's Actually a DNS Issue
Before troubleshooting DNS specifically, do a quick test to confirm that's really the problem. If some websites you've visited recently still load (their address may be cached) while brand new ones fail entirely, or if the error message specifically says "DNS server not responding," this points clearly at DNS rather than a broader connection failure.
Step 2: Restart Your Router First
This sounds repetitive if you've read other troubleshooting guides on this site, but it genuinely resolves a large share of DNS issues, because many home routers also act as a local DNS relay, and that specific function can get stuck without the rest of your internet connection being affected at all.
How to do it properly: unplug the router for a full 30 seconds, not just a few seconds, then plug it back in and wait a full two to three minutes for it to fully reconnect before testing again.
Step 3: Try a Different DNS Provider
Your router is usually configured to use your internet provider's default DNS servers, and occasionally those specific servers experience their own outages or slowdowns, separate from your internet connection working normally otherwise. Switching to a well-known public DNS provider is a common and effective fix.
On Windows: Settings → Network & Internet → your active connection → Edit DNS settings → switch from "Automatic" to "Manual" and enter a public DNS provider's addresses.
On macOS: System Settings → Network → select your active connection → Details → DNS → add the public DNS addresses.
Changing it at the router level applies the fix to every device in your home at once, while changing it on just your computer is faster to test.
Step 4: Flush Your DNS Cache
Your computer keeps a local cache of recently resolved addresses, and occasionally that cache becomes outdated or corrupted, causing failures even when the actual DNS servers are working fine.
On Windows: Open Command Prompt and type ipconfig /flushdns, then press Enter.
On macOS: Open Terminal and type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder, then press Enter.
This is a safe, reversible action that takes seconds and often resolves lingering DNS errors that a simple restart doesn't fully clear.
Step 5: Check Whether It's Your VPN
If you connect through a company VPN, DNS resolution sometimes routes through the VPN's own DNS servers, and a problem there can produce exactly this error even though your home internet is fine — a different pattern from the connection failures covered in our guide on VPN connections that won't connect at all, since here the VPN connects fine but DNS resolution over it doesn't.
Step 6: Temporarily Disable Third-Party Antivirus as a Test
Some antivirus suites include their own DNS filtering, and occasionally these misconfigure themselves. Temporarily disabling third-party antivirus and testing again isolates whether this is a factor.
Step 7: Check If It's Actually Your ISP
If the problem affects your whole household rather than one device, the issue may sit with your provider's DNS infrastructure. Switching to a public DNS provider often works around this even when the cause is on your ISP's side.
Quick Reference
| Symptom | Likely cause | First fix |
|---|---|---|
| Some sites load, new ones don't | Classic DNS resolution failure | Flush DNS cache, restart router |
| Happens on every device in the house | Router-level or ISP DNS outage | Restart router; switch to public DNS at router level |
| Only happens on one computer | Local cache or antivirus conflict | Flush DNS cache; test with antivirus disabled |
| Only happens over VPN | VPN's DNS routing issue | Report to IT; compare with VPN disconnected |
If your computer is company-managed, check with IT before changing DNS settings manually, since some organizations require traffic to route through a specific DNS server.