How Do I Fix DNS Server Not Responding?

Quick Answer

In most cases, DNS Server Not Responding is fixed by power cycling the modem and router, flushing the local DNS cache, and switching the device to a public DNS like Cloudflare (1.1.1.1) or Google (8.8.8.8).

The error means your computer can reach the network but cannot translate website names into IP addresses. The DNS server your provider assigned is busy, crashed, or unreachable.

Run the four tiers below in order. Eight out of ten cases clear at tier 1 or tier 2 without any advanced settings.

What DNS actually does

The Domain Name System is the address book of the internet. When you type google.com, your device asks a DNS server for the matching IP address (for example 142.250.190.46) and only then loads the page.

Your router is usually configured to use the DNS servers run by your internet provider. If those servers are overloaded, misconfigured, or temporarily down, every website fails even though the WiFi icon shows you are connected.

Tier 1: power cycle the network

1. Unplug the power from both the modem and the router.
2. Shut down the computer.
3. Wait a full 60 seconds so the volatile memory in the network gear drains.
4. Plug the modem back in first and wait until its lights are solid.
5. Plug the router back in and wait about two minutes for the WiFi network to come up.
6. Boot the computer and try loading a page.

A power cycle clears a stuck DHCP lease, a frozen routing table, or a crashed DNS resolver inside the router itself.

Tier 2: flush the local DNS cache

Both Windows and macOS keep a local cache of recent DNS lookups. If an entry is stale or corrupt, every visit to that site fails until the cache is cleared.

Windows 10 and 11

1. Press Windows + S, type cmd, right click Command Prompt and choose Run as administrator.
2. Type ipconfig /flushdns and press Enter. You should see "Successfully flushed the DNS Resolver Cache".
3. Run ipconfig /release followed by ipconfig /renew to grab a fresh IP from the router.
4. Restart the browser and test.

macOS

1. Open Finder, go to Applications, Utilities, and launch Terminal.
2. Paste sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder and press Enter.
3. Type your admin password when prompted.
4. Reload the browser.

Tier 3: switch to a public DNS provider

If your internet provider's DNS is the actual problem, point the device at a faster, more reliable public resolver.

Two excellent free options:

• Cloudflare: 1.1.1.1 and 1.0.0.1 (privacy focused, often the fastest)
• Google: 8.8.8.8 and 8.8.4.4 (very reliable, widely supported)

Set DNS on Windows 11

1. Open Settings, Network and internet, WiFi (or Ethernet) and click the active connection.
2. Find DNS server assignment and click Edit.
3. Change Automatic (DHCP) to Manual and toggle IPv4 on.
4. Enter 1.1.1.1 as Preferred and 1.0.0.1 as Alternate.
5. Click Save and reload the browser.

Set DNS on macOS

1. Open System Settings, Network, and select your active connection.
2. Click Details, then DNS.
3. Click the plus sign and add 1.1.1.1, then 1.0.0.1.
4. Click OK, then Apply.

Set DNS on the router (best option)

Changing DNS on the router pushes the new resolver to every phone, laptop, and smart device on the network at once. Log into the router admin page (often 192.168.0.1 or 192.168.1.1), find WAN or Internet settings, and replace the ISP DNS values with 1.1.1.1 and 1.0.0.1.

Tier 4: reset the TCP/IP stack

If the error survives all of the above, the operating system network drivers may be corrupted.

Windows: reset the stack

In an elevated Command Prompt, run these three commands one at a time:

• netsh winsock reset
• netsh int ip reset
• ipconfig /flushdns

Restart the computer.

macOS: renew the DHCP lease

System Settings, Network, click your connection, Details, TCP/IP, and click Renew DHCP Lease. Then restart.

Other fixes worth trying

• Disable VPN or proxy. A misconfigured VPN often blocks DNS lookups while leaving the rest of the connection intact.
• Boot into Safe Mode with Networking. If DNS works in Safe Mode, a third party security app on the main install is interfering.
• Update network drivers. On Windows, open Device Manager, expand Network adapters, right click your WiFi or Ethernet adapter, and choose Update driver.
• Temporarily disable the firewall and antivirus. Just long enough to test. If DNS works with them off, add an exception rather than leaving them disabled.

FAQs

Will changing my DNS speed up the internet?

It can. Cloudflare and Google often answer faster than smaller ISP resolvers, which reduces page load times slightly, especially on sites you have not visited recently. It does not change your raw bandwidth.

Is 1.1.1.1 safe to use?

Yes. Cloudflare's resolver is widely audited, does not log personally identifiable queries, and is used by millions of people and businesses.

Why does the error come back after a reboot?

If the DNS setting on the device is Automatic, the router pushes its own DNS back each time. Set the public DNS on the router itself for a permanent fix.

Does this fix work on a Chromebook or phone?

Yes. Both Android and iOS let you set custom DNS per WiFi network in WiFi settings. Chromebooks expose the same option under Network details.

The takeaway

Power cycle the modem and router, flush the cache, then move the device or the router to 1.1.1.1. That ladder fixes the DNS Server Not Responding error for the vast majority of users without any advanced terminal work.