Network settings screen showing DNS server configuration with error indicator

Domain Management

DNS Server Not Responding: Causes and Fixes for Windows, Mac, and Router

Domain 360 Team

·July 8, 2026·7 min read

"DNS server not responding" tells you something specific: your device is online but cannot reach the server responsible for translating domain names to IP addresses. The internet connection is technically there — the translation layer is broken. Here is the fix sequence.

Quick answer: "DNS server not responding" means your device cannot reach the server that translates domain names to IP addresses. Here is the diagnostic sequence that fixes it 90% of the time — and what to try when it does not.

Step 1: Restart Your Router

Sounds too simple. It fixes the problem more often than any other step. Routers maintain their own DNS cache and DNS server connections, which can stall or corrupt over days of continuous operation.

Unplug the router power cable, wait 30 seconds, plug it back in. Wait 60 seconds for it to fully reconnect. Test your connection.

If multiple devices on your network were affected and they all work after the router restart, the router was the cause. If only one device is affected, continue to the next steps.

Step 2: Flush DNS Cache

If the router restart did not help, clear the stale cached records on your device.

Windows: open Command Prompt as administrator, run ipconfig /flushdns. Mac: open Terminal, run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

Full instructions for every OS are in our DNS flush guide.

Step 3: Change Your DNS Server

This is the most effective fix for ISP-related DNS failures and often works within seconds of applying it.

Windows 11: Settings, Network and Internet, your connection, Hardware and connection properties, DNS server assignment, Edit, Manual, enter 1.1.1.1 and 1.0.0.1 (Cloudflare) or 8.8.8.8 and 8.8.4.4 (Google).

Windows 10: Control Panel, Network and Sharing Center, Change adapter settings, right-click your connection, Properties, Internet Protocol Version 4, Properties, Use the following DNS server addresses, enter the addresses above.

Mac: System Settings, Network, your connection, Details, DNS, click the + and add 1.1.1.1 and 8.8.8.8.

After changing and saving, try loading a website. If it works, your ISP DNS was the problem.

Step 4: Check Network Adapter

On Windows, open Device Manager (search for it in Start). Look under Network adapters for any devices showing a yellow warning icon. If you see one on your network adapter, right-click and choose Update driver, or Uninstall device and then scan for hardware changes to reinstall it.

Step 5: Disable Security Software Temporarily

Antivirus programs with network monitoring, firewalls, and VPN software can all intercept DNS queries and cause failures. Temporarily disabling each of them — one at a time — helps identify if software is the cause.

If DNS works with your antivirus disabled, check its settings for DNS interception or HTTPS scanning features, which sometimes conflict with system DNS settings.

Step 6: Reset Network Settings

Windows: open Command Prompt as administrator and run these commands in sequence: netsh winsock reset netsh int ip reset ipconfig /release ipconfig /renew ipconfig /flushdns

Restart your computer afterward. This resets the network stack and often clears problems that persist through simpler fixes.

What If None of This Works?

If the problem only appears for specific websites while others load fine, the issue is those domains specifically rather than your DNS server. Run a WHOIS lookup on the affected domain to check whether it is registered and has valid nameservers. A recently expired domain produces DNS failure symptoms that look identical to a DNS server problem — but the fix is domain renewal, not network troubleshooting. Our WHOIS lookup tool takes five seconds to rule this out.

Quick Answers

What does "DNS server not responding" mean?

It means your device tried to contact the configured DNS server to look up a domain name, and the server did not respond. Without a working DNS server, no domain names resolve — no websites load, even though your internet connection may be technically active. The fault is usually your DNS server, your router, or your network settings.

How do I fix DNS server not responding?

The standard fix sequence: 1) Restart your router (most common fix). 2) Flush your DNS cache. 3) Change your DNS server to 8.8.8.8 or 1.1.1.1. 4) Check for network adapter issues via Device Manager. 5) Temporarily disable antivirus and firewall to test. Most cases resolve at step 1 or 3.

Why is DNS server not responding on only my computer?

If other devices on the same network work fine, the problem is your specific device rather than your router or ISP. Check your network adapter settings, flush DNS cache, try a different DNS server, and check for conflicting software. Disabling VPNs and antivirus temporarily helps identify software conflicts.

Can my ISP cause DNS server not responding?

Yes. If your ISP DNS servers are down, all devices on your network will fail to resolve domain names simultaneously. Switching to a public DNS server like 1.1.1.1 or 8.8.8.8 bypasses your ISP DNS completely and usually restores browsing immediately.

Should I change DNS to 8.8.8.8 to fix this?

Changing to Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) is an effective fix when your ISP or router DNS server is causing the problem. These public servers are highly reliable and generally faster than ISP defaults. The change takes effect immediately after saving network settings.

Never lose a domain again

Track every domain you own in one dashboard. Free for up to 15 domains.