Google Chrome ERR_DNS_SERVER_FAILED: How to Fix It

Easy 10-30 minutes Medium Severity Verified June 2026
Summarize with ChatGPTSummarize with ClaudeSummarize with Perplexity Add as Preferred Source on Google
Error Code
ERR_DNS_SERVER_FAILED
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_DNS_SERVER_FAILED error in Google Chrome means your browser tried to look up a website's address but the DNS server — the internet's phone book — returned an error or failed to respond. This can be caused by a faulty DNS server, a misconfigured network adapter, or problems with Chrome's own DNS cache. The good news is that most cases are fixable in minutes without any technical background.
Ad

Tools You'll Need

How to Fix Error Code ERR_DNS_SERVER_FAILED

  1. Check Your Internet Connection

  2. Flush Chrome's Internal DNS Cache

  3. Flush Your Operating System DNS Cache

  4. Change Your DNS Server to a Public DNS

  5. Reset Your Network Stack (Windows)

    Running these commands will temporarily disconnect your network. Save any open work before proceeding.

  6. Disable Chrome's Secure DNS Feature

  7. Disable VPN or Proxy Settings

  8. Update or Reinstall Network Adapter Drivers (Windows)

  9. Reset or Reinstall Google Chrome

    Resetting Chrome will disable all extensions. Re-enable only trusted ones after the reset, as a rogue extension may have caused the problem.
Ad

When to Call a Professional

If you have completed all steps above and the error still appears on every website in Chrome as well as other browsers, your ISP's DNS infrastructure may be experiencing an outage. Contact your internet service provider's technical support line and describe the ERR_DNS_SERVER_FAILED error. If the error only happens on a business or school network, contact your network administrator, as the DNS server may be managed and restricted by your organization. If your router's firmware is outdated or misconfigured, a networking professional or your ISP can assist with that as well.

Frequently Asked Questions

What does ERR_DNS_SERVER_FAILED mean in Chrome?
It means Chrome sent a DNS lookup request to find the IP address of a website but the DNS server responded with an error or did not respond at all. DNS servers work like a phone book for the internet, translating domain names like 'example.com' into numeric IP addresses. When the server fails, Chrome cannot locate the site and shows this error.
Why does ERR_DNS_SERVER_FAILED only happen on certain websites?
If the error only affects specific websites, those sites' own DNS records may be misconfigured or their hosting provider may be experiencing issues. It could also be that Chrome's cache has a corrupted entry specifically for those domains. Try flushing Chrome's DNS cache (chrome://net-internals/#dns) and clearing the host cache to fix site-specific errors.
Will changing my DNS to Google or Cloudflare fix ERR_DNS_SERVER_FAILED?
In many cases, yes. If your ISP's DNS server is slow, overloaded, or temporarily down, switching to Google Public DNS (8.8.8.8 / 8.8.4.4) or Cloudflare DNS (1.1.1.1 / 1.0.0.1) bypasses your ISP's server entirely and often resolves the error immediately. These free public DNS servers are fast, reliable, and widely recommended.
Can a VPN cause ERR_DNS_SERVER_FAILED in Chrome?
Yes. VPNs route your DNS requests through their own servers, and if the VPN server is down, misconfigured, or experiencing a DNS leak, Chrome may show this error. Try disabling your VPN temporarily and reloading the page. If the error disappears, the issue is with your VPN's DNS settings, and you may need to contact your VPN provider or switch DNS servers within the VPN app's settings.
Does ERR_DNS_SERVER_FAILED mean a website is down?
Not necessarily. The error is usually a problem on your end with your DNS server, network configuration, or Chrome settings. However, if you have tried all fixes and only one specific website fails, that site's DNS records may genuinely be broken or the site may be down. You can verify by checking the site on a downdetector tool or from a different network like your mobile data connection.

Related Error Codes