Google Chrome ERR_DNS_PROBE_FINISHED_BAD_CONFIG: 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_PROBE_FINISHED_BAD_CONFIG
Brand
Google Chrome
Product Type
browser
Severity
Medium
DIY Difficulty
Easy
Estimated Fix Time
10-30 minutes
The ERR_DNS_PROBE_FINISHED_BAD_CONFIG error in Google Chrome means your browser cannot translate a website's domain name into an IP address because your DNS (Domain Name System) configuration is invalid, corrupted, or misconfigured. This is typically a network or system-level issue — not a problem with the website itself — and it prevents Chrome from loading any page affected by the bad DNS settings. The good news is that in most cases you can resolve it yourself in just a few minutes by flushing your DNS cache, switching your DNS server, or resetting your network settings.
Ad

Tools You'll Need

How to Fix Error Code ERR_DNS_PROBE_FINISHED_BAD_CONFIG

  1. Reload the Page and Check Your Internet Connection

  2. Flush Your DNS Cache (Windows)

    Run Command Prompt as Administrator — running it as a standard user will cause the commands to fail silently.

  3. Clear Chrome's Internal DNS Cache

  4. Change Your DNS Server to a Public DNS

    Write down your original DNS settings before changing them so you can revert if needed.

  5. Reset TCP/IP and Winsock (Windows)

    This reset can occasionally cause issues with VPN software or specialized network adapters. If you use a VPN, you may need to reinstall it after this step.

  6. Disable VPN, Proxy, or Firewall Temporarily

    Only disable your firewall or antivirus temporarily for testing purposes. Re-enable it immediately after diagnosing the issue.

  7. Update Your Network Adapter Driver

  8. Restart Your Router and Modem

  9. Reset Chrome Flags and Settings to Default

    Resetting Chrome settings will disable all extensions and clear pinned tabs. Make note of any important extensions before proceeding.
Ad

When to Call a Professional

If you have completed all steps above and the error persists across multiple browsers (not just Chrome), the issue likely lies with your ISP's DNS infrastructure or your router's firmware. Contact your Internet Service Provider's technical support line — they can check for outages, reset your connection from their end, or push a firmware update to your modem. If the issue only occurs on a managed work or school network, contact your IT administrator, as DNS settings on corporate or institutional networks are often locked down and cannot be changed by the end user.

Frequently Asked Questions

What does ERR_DNS_PROBE_FINISHED_BAD_CONFIG mean in Chrome?
It means Chrome attempted to look up the IP address for a website's domain name but found that your DNS (Domain Name System) configuration is invalid or broken. Chrome cannot connect to the site because the system responsible for translating domain names (like 'google.com') into IP addresses is not working correctly on your device or network.
Does ERR_DNS_PROBE_FINISHED_BAD_CONFIG mean the website is down?
Not usually. This error almost always points to a problem on your end — specifically with your DNS settings, network adapter, or router — rather than the website being offline. To confirm, try accessing the same site on a different device or network (like mobile data). If it loads there, the issue is with your local DNS configuration.
Will changing my DNS to Google (8.8.8.8) fix the ERR_DNS_PROBE_FINISHED_BAD_CONFIG error?
Switching to Google's public DNS servers (8.8.8.8 and 8.8.4.4) or Cloudflare's servers (1.1.1.1 and 1.0.0.1) is one of the most effective fixes for this error. If your ISP's DNS servers are misconfigured or experiencing an outage, switching to a reliable public DNS will bypass the problem entirely and usually resolves the error immediately.
Why does ERR_DNS_PROBE_FINISHED_BAD_CONFIG only happen on Chrome and not other browsers?
Chrome has its own internal DNS cache and performs its own DNS probe checks separate from your operating system. If Chrome's internal DNS cache is corrupted while other browsers use the OS-level cache, you may see this error only in Chrome. Clearing Chrome's internal DNS cache at 'chrome://net-internals/#dns' and flushing socket pools typically resolves Chrome-specific occurrences.
Can a VPN cause ERR_DNS_PROBE_FINISHED_BAD_CONFIG?
Yes. VPN clients sometimes override your DNS settings or route DNS requests through their own servers, which can become misconfigured or go offline. If you use a VPN, try disabling it temporarily and refreshing the page. If the error disappears, the issue is with your VPN's DNS configuration. Check your VPN app's settings, update the app, or contact your VPN provider's support team.

Related Error Codes