How To • Troubleshoot • DNS & Connectivity

How to fix DNS server not responding

This guide will help you diagnose and resolve "DNS server not responding" errors, which prevent your devices from accessing websites. You'll learn to quickly identify the cause and apply targeted fixes, from simple restarts to configuring more reliable DNS servers.

Note: Steps may vary by device and router model. This guide focuses on safe, general methods.

Quick Answer

Restart your router and modem by unplugging them for 30 seconds.
Restart the affected device (computer, phone, etc.).
Try a different network (switch from Wi-Fi to mobile data on your phone) to see if the problem is with your home network.
Flush your DNS cache.

Windows (Command Prompt as Admin): Type ipconfig /flushdns

macOS (Terminal): Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder
Change your DNS server to a public one like Google (8.8.8.8) or Cloudflare (1.1.1.1) in your device or router settings.

If these steps don't work, follow the diagnostic flow and detailed steps below.

What you need

Before you start

Access to the device with the problem (computer, phone, tablet).
Your Wi-Fi network name and password.
Your router's admin login details (often on a sticker on the router).
Basic ability to navigate your device's network settings.

Good to know

DNS (Domain Name System) translates website names (like luvvhelp.com) into numerical IP addresses.
Your ISP provides a default DNS server, but you can use public alternatives.
Commands like ping and nslookup can test connectivity.
VPNs and some security software can interfere with DNS.

Diagnose the issue in 2 minutes

Is it only one device or all devices on your network?
- One device: The problem is likely on that device (software, cache, settings).
- All devices: The problem is likely with your router or Internet Service Provider (ISP).
For the affected device, can you access anything online?
- No internet at all: Broader connection issue, not just DNS. Check cables, Wi-Fi, router lights.
- Some sites work (like Google), but others don't: Classic sign of a DNS problem.
- Ping test: Open Command Prompt (Windows) or Terminal (macOS/Linux) and type ping 8.8.8.8. If you get replies, your internet connection is working but DNS is not.
Are you using a VPN or custom security software? Temporarily disable it. If the problem goes away, the VPN/software DNS settings are the cause.
Quick Checks:
1. Check if airplane mode is off and Wi-Fi/Ethernet is connected.
2. Cycle the connection (turn Wi-Fi off/on).
3. Note if the error message mentions a specific DNS server address.

Step-by-step guide

Step 1 — Restart everything

Power cycling clears temporary glitches in devices and network hardware.

Unplug your modem and router from power.
Wait at least 30 seconds.
Plug the modem back in, wait for all its lights to stabilize.
Then plug the router back in and wait for it to fully boot.
Finally, restart the computer or device having the issue.

What you should see: A fresh connection. Try browsing again.

Step 2 — Flush the local DNS cache

Your device stores DNS lookups locally; this cache can become corrupted.

Windows: Open Command Prompt as Administrator. Type ipconfig /flushdns and press Enter. You should see "Successfully flushed the DNS Resolver Cache."

macOS: Open Terminal. Type sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter. You'll need to enter your password.

Linux: The command depends on your distro. For systemd-resolved, use sudo systemd-resolve --flush-caches.

What you should see: No immediate visual change, but old, bad DNS records are cleared.

Step 3 — Disable VPN and security software temporarily

VPNs and firewalls often use their own DNS servers, which may fail.

Fully exit your VPN application.
Temporarily disable third-party firewalls or "internet security" suites.
Try browsing again. If it works, reconfigure your VPN's DNS settings or check your security software's network rules.

What you should see: Internet access returns immediately after disabling.

Step 4 — Change DNS server on your device

Bypass your ISP's potentially problematic DNS by using a reliable public server.

Windows: Go to Settings > Network & Internet > Change adapter options. Right-click your connection > Properties. Select "Internet Protocol Version 4 (TCP/IPv4)" > Properties. Choose "Use the following DNS server addresses". Enter 8.8.8.8 (Preferred) and 8.8.4.4 (Alternate) for Google DNS.

macOS: System Settings > Network. Select your connection > Details > DNS. Click the + button and add 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google).

General: You can also use 1.1.1.1 (Cloudflare) or 9.9.9.9 (Quad9).

What you should see: Websites start loading. This is often the definitive fix for device-specific DNS issues.

Step 5 — Change DNS server on your router

This applies the fix to every device on your network automatically.

Log into your router's admin panel (usually via a web browser, address like 192.168.1.1 or 192.168.0.1).
Navigate to the WAN or Internet settings section.
Look for a DNS server field. Change from "Obtain automatically from ISP" to manual.
Enter the public DNS addresses (e.g., 1.1.1.1 and 8.8.8.8).
Save settings and reboot the router.

What you should see: All devices on your network now use the new, reliable DNS servers.

Step 6 — Update network drivers and firmware

Outdated software can cause compatibility issues with modern DNS protocols.

Device Drivers (Windows): Open Device Manager, find your network adapter, right-click and select "Update driver."
Router Firmware: In your router's admin panel, check the Administration or Firmware update section.
Operating System: Ensure your OS has all the latest updates installed.

What you should see: Improved stability and potentially new features that prevent DNS errors.

Common fixes by symptom

Symptom: "Connected but no internet" on all devices

Likely causes: Router failure, modem failure, ISP outage, incorrect router WAN settings.

Safe fixes: Power cycle modem/router, check modem lights for upstream signal, log into router to see if it has a WAN/IP address from the ISP.

When to escalate: If modem lights indicate no signal (e.g., no steady "online" light) – contact ISP.

Symptom: Some websites don't open, but others do

Likely causes: DNS server failure, DNS cache poisoning, ISP DNS filtering.

Safe fixes: Flush DNS cache on device, change device DNS to 1.1.1.1 or 8.8.8.8, try opening site in a different browser.

When to escalate: If the problem persists across all devices even after changing router DNS – possible ISP-level issue.

Symptom: Error only on one computer (wired or Wi-Fi)

Likely causes: Corrupted network settings, outdated drivers, aggressive firewall, malware.

Safe fixes: Run network troubleshooter (Windows), renew IP lease (ipconfig /release then /renew), update network adapter drivers, scan for malware.

When to escalate: If malware is suspected and cannot be removed with standard tools.

Symptom: Internet works until you connect a VPN

Likely causes: VPN's DNS server is unreachable, VPN kill switch is active, conflict with local DNS.

Safe fixes: Try different VPN servers, change VPN protocol (e.g., from OpenVPN to WireGuard), check VPN app settings for DNS options.

When to escalate: Contact your VPN provider's support with details of the error.

Symptom: Intermittent "DNS Server Not Responding"

Likely causes: Unstable internet connection, overheating router, IP address conflict.

Safe fixes: Ensure router is ventilated, use a static DNS on your device (Step 4), check for too many devices overloading the router.

When to escalate: If the router consistently drops connection – it may need replacement.

Quick reference

Table A: What the metric means

Metric	What it is	Good Baseline
Latency (Ping)	Time for a data packet to go to a server and back.	< 50 ms (lower is better)
Jitter	Variation in latency. High jitter causes stuttering.	< 10 ms
Packet Loss	Percentage of data packets that never arrive.	0%
Throughput	Actual download/upload speed you experience.	Close to your ISP's advertised plan.
Signal Strength	Power of the Wi-Fi signal your device receives.	-50 dBm to -60 dBm (excellent). Below -70 dBm is poor.

Table B: Safe baseline settings

Category	Recommended Setting
Wi-Fi Security	WPA2/WPA3 Personal (AES). Avoid WEP or TKIP.
DNS Servers	Cloudflare (1.1.1.1) or Google (8.8.8.8) for reliability.
Router Admin	Change default login password. Keep firmware updated.
Guest Network	Enable for visitors. Isolates them from your main devices.
Updates	Check for router firmware updates every 3-6 months.

Mind map summary

DNS Server Not Responding
|
+-- Is it ONE device or ALL devices?
|   |
|   +-- ONE Device
|   |   +-- Flush DNS Cache (ipconfig /flushdns)
|   |   +-- Change Device DNS to 1.1.1.1
|   |   +-- Update Network Drivers
|   |   +-- Disable VPN/Security Software
|   |
|   +-- ALL Devices
|       +-- Restart Router/Modem
|       +-- Change Router DNS Settings
|       +-- Check for ISP Outage
|
+-- Can you PING 8.8.8.8? (Command Prompt/Terminal)
|   |
|   +-- YES: Internet works, DNS is broken.
|   |   +-- Primary Fix: Change DNS Server.
|   |
|   +-- NO: General connection problem.
|       +-- Check cables, modem lights, Wi-Fi connection.
|
+-- Quick Wins (try first)
    +-- Power Cycle Everything
    +-- Switch Wi-Fi to Mobile Data (to test)
    +-- Use a different browser

Troubleshooting checklist

Device

Restart the device
Flush DNS cache
Toggle Airplane mode / Wi-Fi
Change DNS settings on device
Update network drivers / OS
Disable VPN & extra firewalls

Router / Network

Power cycle router & modem
Log in, check connection status
Change DNS settings in router
Check for firmware update
Try connecting via Ethernet cable
Reduce number of connected devices

ISP & External

Check ISP outage map / status
Test with a different network (e.g., phone hotspot)
Note modem indicator lights
Call ISP with error details ready

When to escalate

Contacting your ISP: When the problem affects all devices, your modem shows no "online" or "signal" light, or you've confirmed an area outage. Also contact them if changing DNS servers doesn't help and the issue is persistent.
Replacing your router: If it constantly drops connections, overheats, cannot be updated to current security standards, or fails to maintain settings after a reboot.
Asking IT support (for work devices): If you're on a managed corporate network, your device has strict group policies, or you suspect the issue is related to enterprise security software.

What to collect before you call:

Exact error message and when it started.
Results from a speed test and a ping test to 8.8.8.8.
Whether the problem is on Wi-Fi, Ethernet, or both.
Model numbers of your modem and router.
Any troubleshooting steps you've already tried.

FAQ

Is it safe to use public DNS servers like Google or Cloudflare?

Yes, in most cases. These public DNS services are reputable, often faster and more reliable than some ISP-provided servers. They may also offer additional privacy features (like Cloudflare's 1.1.1.1) or security filtering (like Quad9's 9.9.9.9).

Will changing my DNS affect my internet speed?

It can, but usually for the better. A faster, more efficient DNS server can make websites feel like they load quicker because the initial name lookup is faster. It won't increase your raw download speed from a speed test, but it can improve browsing responsiveness.

Why does restarting the router fix DNS issues so often?

Routers are small computers that can develop software glitches or run out of memory. Restarting clears the router's temporary memory (RAM), kills any stuck processes, and forces it to re-establish fresh connections with your ISP and its assigned DNS servers.

What's the difference between "DNS Server Not Responding" and "No Internet Access"?

"DNS Server Not Responding" means your device can't contact the phonebook (DNS) to look up website addresses, but the underlying internet connection might be fine. "No Internet Access" usually indicates a broader failure—your device can't reach the network gateway or internet at all.

Should I use my router's IP address as my DNS server?

This is a common default setting. Your router often acts as a "DNS forwarder," taking requests from your devices and passing them to the ISP's DNS. If the router's DNS service is buggy, setting your device to use 1.1.1.1 directly bypasses it, which can solve the problem.

Can antivirus software cause DNS errors?

Yes. Some security suites include features that filter web traffic or use their own secure DNS servers. If these components malfunction or conflict, they can block valid DNS requests. Temporarily disabling the antivirus network protection can help diagnose this.

What is DNS over HTTPS (DoH) and should I enable it?

DoH encrypts your DNS queries, preventing others on your network from seeing which websites you look up. It can enhance privacy. You can enable it in modern browsers (like Firefox or Chrome) or in your OS settings. If your current DNS fails, enabling DoH might bypass the problem.

How do I know if my ISP is blocking a DNS server?

If you manually set a public DNS (like 1.1.1.1) and still get errors, try pinging that DNS server IP. If it times out but you can ping other IPs (like 8.8.8.8), your ISP might be blocking the first one. Try an alternate public DNS server from a different provider.

Sources and references

Microsoft Windows Documentation for network commands (ipconfig, ping, nslookup).
Apple macOS Support documentation for network utility and DNS management.
Linux man pages for systemd-resolved, dig, and network configuration.
General networking concepts from CompTIA Network+ and Cisco networking fundamentals.
Router manufacturer administration guides for DNS configuration procedures.
Internet Engineering Task Force (IETF) RFCs on DNS protocols and operation.
Cybersecurity best practices for home networks from CISA and other security organizations.
Public DNS service documentation from Cloudflare, Google, and Quad9.

Menu

How to fix DNS server not responding

AI Assistant

Was this tool helpful?