DNS Server Not Responding: The Complete Fix

Published 2026 - 4 min read

DNS failure means your device cannot turn names like fixhubhq.com into IP addresses. Sites fail to load even though the internet itself is up.

1. Confirm it is DNS

Open Command Prompt and run ping 8.8.8.8. If that works but websites do not, it is DNS. Run nslookup google.com - an error here confirms the resolver is the problem.

2. Restart the router

Routers cache DNS and can serve stale or broken entries. Power it off for 30 seconds and back on, then reboot the PC.

3. Flush the local cache

In Command Prompt run ipconfig /flushdns to clear Windows' resolver cache. This instantly fixes many "DNS server not responding" messages.

4. Switch to a public DNS

Open Network Connections > your adapter > Properties > IPv4 > Properties and set DNS to 1.1.1.1 and 8.8.8.8. Do the same on the router (DHCP DNS) so every device benefits.

5. Reset the network stack

Run these in an elevated Command Prompt, then reboot: netsh winsock reset and netsh int ip reset.

6. Check security software

Some antivirus and firewall suites override DNS. Temporarily disable the protection to test, then re-enable and add your DNS servers to its allow list.

Hardware note: Public DNS (1.1.1.1, 8.8.8.8) is usually faster and more reliable than your ISP's servers, and it is safe to use permanently.

Prevention: Set your preferred public DNS at the router level (DHCP) so every phone, PC and TV gets the reliable resolver without per-device setup. If outages keep returning, update the router firmware - stale router DNS firmware is a common cause of intermittent failures.