How to Fix DNS Server Not Responding Error in Chrome

If Chrome is showing a DNS Server Not Responding error while opening a website, it usually means your device is unable to communicate properly with the DNS server.

DNS, or Domain Name System, converts website domain names into IP addresses. When the DNS server is unavailable, incorrectly configured, or not responding, Chrome may fail to load websites.

This problem can be caused by your internet connection, router, DNS cache, DNS settings, VPN, firewall, ISP, or even the website's DNS configuration.

In this guide, we'll explain how to fix the DNS Server Not Responding error in Chrome step by step.

What Does DNS Server Not Responding Mean?

When you enter a domain such as:

example.com

your device sends a DNS request to find the IP address associated with that domain.

If the DNS server doesn't respond correctly, your browser cannot determine where the website is hosted.

As a result, Chrome may show an error such as:

DNS Server Not Responding

or:

This site can't be reached

The problem may exist on your computer, network, DNS provider, or the website's DNS configuration.

Common Causes of DNS Server Not Responding

Some common causes include:

• Unstable internet connection

• DNS server outage

• Incorrect DNS settings

• Corrupted DNS cache

• Router problems

• Outdated network configuration

• VPN or proxy interference

• Firewall or security software

• Incorrect IPv4 or IPv6 configuration

• ISP DNS problems

• Incorrect domain DNS records

• Hosting or VPS DNS problems

Let's go through the solutions one by one.

1. Check Your Internet Connection

Before changing DNS settings, make sure your internet connection is working.

Try opening several different websites.

If none of them work, the problem may be your internet connection rather than DNS specifically.

You can try:

• Disconnecting and reconnecting Wi-Fi

• Restarting your router

• Connecting through mobile hotspot

• Testing another device on the same network

If websites work on mobile data but not on your Wi-Fi, your router, ISP, or DNS configuration may be responsible.

2. Restart Your Router

Restarting your router can fix temporary DNS and network problems.

Turn off the router and wait for about 30 seconds.

Then turn it back on and wait until the internet connection is restored.

Open Chrome and try accessing the website again.

3. Restart Your Computer

A temporary network service or DNS problem can sometimes be fixed simply by restarting your device.

Close your applications, restart your computer, reconnect to the internet, and test the website again.

4. Try Chrome Incognito Mode

Chrome extensions and cached browser data can sometimes interfere with website connections.

Open Chrome Incognito Mode and visit the website again.

If the website works in Incognito Mode, disable your extensions one by one to find the problematic extension.

You can also clear Chrome's browsing data if necessary.

5. Disable VPN or Proxy

VPNs and proxy servers can change your DNS configuration.

If you're using a VPN, disconnect it temporarily and try opening the website again.

Also check your system proxy settings.

If the website starts working after disabling the VPN or proxy, the DNS configuration provided by that service may be causing the problem.

6. Clear Chrome DNS Cache

Chrome maintains its own DNS-related cache.

You can clear it by opening:

chrome://net-internals/#dns

Then click:

Clear host cache

Close and reopen Chrome after clearing the cache.

Now try opening the website again.

7. Flush DNS Cache on Windows

Windows stores DNS information locally.

A corrupted or outdated DNS cache can cause DNS resolution problems.

Open Command Prompt as Administrator and run:

ipconfig /flushdns

You should receive a message confirming that the DNS resolver cache was flushed.

Then restart Chrome.

You can also renew your network configuration:

ipconfig /release
ipconfig /renew

Test the website again.

8. Flush DNS Cache on macOS

If you're using macOS, you can flush the DNS cache using:

sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder

Enter your password if macOS asks for it.

Then reopen Chrome and test the website.

9. Flush DNS Cache on Linux

On Ubuntu and many Linux distributions using systemd-resolved, run:

sudo resolvectl flush-caches

You can check your current DNS configuration with:

resolvectl status

If your Linux system uses another DNS service, the appropriate command may be different.

10. Change Your DNS Server

Changing the DNS server is one of the most useful solutions for DNS-related problems.

Your ISP's DNS server may be temporarily unavailable or experiencing problems.

You can test public DNS services such as:

Google DNS

8.8.8.8
8.8.4.4

Cloudflare DNS

1.1.1.1
1.0.0.1

After changing the DNS server, reconnect to your network and test the website.

If the website starts working, your previous DNS server was likely the problem.

11. Test DNS Using nslookup

The nslookup command can help determine whether your DNS server is responding.

Run:

nslookup example.com

If DNS is working, the command should return information about the domain, including its IP address.

You can test a specific DNS server as well:

nslookup example.com 8.8.8.8

If the domain resolves through Google's DNS but not through your default DNS server, your default DNS resolver may be experiencing a problem.

12. Use dig to Check DNS

Linux and macOS users can use dig to investigate DNS responses.

Run:

dig example.com

To check the A record:

dig example.com A

To check nameservers:

dig example.com NS

You can also query Cloudflare DNS directly:

dig @1.1.1.1 example.com

These commands are useful when troubleshooting DNS problems on hosting servers and VPS systems.

13. Check Your DNS Records

If the problem affects your own website, check the DNS records at your DNS provider.

The most important records include:

• A record

• AAAA record

• CNAME record

• NS record

For example:

example.com → YOUR_VPS_IP

Make sure the A record points to the correct server IP.

A wrong or missing DNS record can prevent visitors from reaching your website.

14. Check the A Record

An A record connects a domain to an IPv4 address.

For example:

example.com → 203.0.113.10

If your website has moved to another server, make sure the A record has been updated to the new server IP.

Incorrect A records are a common cause of website DNS problems.

15. Check the AAAA Record

An AAAA record is used for IPv6.

If your domain has an AAAA record pointing to an incorrect IPv6 address, some visitors may experience connectivity problems.

Check whether the IPv6 address is correct and that your server is properly configured for IPv6.

If you don't use IPv6, make sure there isn't an unnecessary or incorrect AAAA record.

16. Check Your Nameservers

Nameservers tell the internet which DNS provider manages your domain.

You can check the current nameservers with:

dig example.com NS

Make sure the nameservers configured at your domain registrar match the DNS provider where your records are managed.

If the wrong nameservers are configured, your DNS records may not be found.

17. Check DNS Propagation

If you recently changed DNS records or nameservers, the changes may take some time to appear across different DNS resolvers.

For example, after changing:

• A records

• AAAA records

• CNAME records

• Nameservers

some networks may continue using cached DNS information temporarily.

If the website works from one network but not another, DNS propagation or caching could be responsible.

18. Check Your Domain Expiration

If your website suddenly stops resolving, check whether the domain registration is still active.

Log in to your domain registrar and verify:

• Domain expiration date

• Domain status

• Nameservers

• DNS records

• Registration status

An expired or suspended domain may stop resolving correctly.

19. Check Your Hosts File

Your computer's hosts file can override normal DNS resolution.

On Linux and macOS, it is located at:

/etc/hosts

On Windows:

C:\Windows\System32\drivers\etc\hosts

Look for entries related to the affected domain.

For example:

127.0.0.1 example.com

An incorrect entry can cause your computer to send requests to the wrong address.

Only modify hosts file entries if you're sure they are incorrect.

20. Check Firewall and Security Software

Firewall and security software can sometimes interfere with DNS or network requests.

If the problem started after installing or changing security software, review its network settings.

Make sure DNS traffic and legitimate network connections are not being blocked.

Avoid permanently disabling your firewall just to troubleshoot a DNS problem.

21. Check Router DNS Settings

Some routers allow you to configure DNS servers directly.

Log in to your router's administration panel and check its DNS settings.

If the router is using an unreliable DNS server, try configuring a trusted DNS resolver such as:

1.1.1.1

or:

8.8.8.8

Save the settings and restart the router if required.

22. Check DNS on Your VPS

If your website is hosted on a VPS and visitors are receiving DNS errors, check the domain and server configuration.

Verify:

• Domain points to the correct VPS IP

• A record is correct

• AAAA record is correct

• Nameservers are correct

• DNS zone exists

• Domain is active

• Firewall rules are correct

• Web server is running

For Nginx, check the configuration using:

sudo nginx -t

If DNS resolves correctly but the website still doesn't open, investigate Nginx, Apache, firewall rules, ports, SSL, or the application.

DNS Server Not Responding vs Other Errors

Several Chrome errors can look similar.

DNS Server Not Responding

Usually indicates that your device cannot communicate successfully with the DNS server.

DNS_PROBE_FINISHED_BAD_CONFIG

Usually indicates a DNS configuration or network configuration problem.

DNS_PROBE_FINISHED_NXDOMAIN

Usually means the DNS lookup indicates that the domain doesn't exist or cannot be found.

ERR_NAME_NOT_RESOLVED

Means Chrome was unable to resolve the domain name to an IP address.

ERR_CONNECTION_TIMED_OUT

The domain may resolve, but the destination server does not respond within the expected time.

ERR_CONNECTION_REFUSED

The server is reachable, but the connection is being refused, commonly because the required service or port isn't accepting connections.

Quick Fix Checklist

If Chrome says DNS Server Not Responding, try these steps:

1. Check your internet connection.

2. Restart your router.

3. Restart your computer.

4. Try Chrome Incognito Mode.

5. Disable VPN or proxy.

6. Clear Chrome DNS cache.

7. Flush your operating system DNS cache.

8. Change DNS to 1.1.1.1 or 8.8.8.8.

9. Run nslookup.

10. Test DNS using dig.

11. Check A and AAAA records.

12. Verify CNAME records.

13. Check your nameservers.

14. Check DNS propagation.

15. Verify domain expiration.

16. Check your hosts file.

17. Review firewall settings.

18. Check router DNS settings.

19. Check your hosting or VPS DNS configuration.

How to Prevent DNS Problems

You can reduce DNS-related issues by following good DNS management practices:

• Use reliable DNS providers.

• Keep your domain registration active.

• Keep DNS records accurate.

• Avoid unnecessary nameserver changes.

• Monitor important domains and subdomains.

• Keep VPS IP addresses updated in DNS.

• Document DNS changes.

• Regularly check A, AAAA, CNAME, and NS records.

• Avoid incorrect DNSSEC configurations.

• Monitor your hosting server and network.

Conclusion

The DNS Server Not Responding error in Chrome usually means that your device cannot get a valid response from its configured DNS server.

The easiest solutions are to restart your router, clear DNS cache, flush your system's DNS cache, and try a different DNS server such as Cloudflare or Google DNS.

If the problem affects your own website, check the domain's DNS records, nameservers, DNS propagation, hosting configuration, and VPS settings.

Once your DNS server responds correctly and the domain resolves to the correct IP address, Chrome should be able to connect to the website normally.