How to Fix “DNS_PROBE_FINISHED_BAD_CONFIG” in Google Chrome

Attempting to load any website in Google Chrome only to be stopped by an error screen stating “This site can’t be reached” alongside the error code DNS_PROBE_FINISHED_BAD_CONFIG is an immediate roadblock. Unlike errors targeting a single unresponsive server, this diagnostic code indicates that your local system cannot resolve domain names for any address on the internet.

The DNS_PROBE_FINISHED_BAD_CONFIG error occurs when Google Chrome attempts to translate a human-readable URL (such as example.com) into an IP address, but finds that your operating system’s Domain Name System (DNS) resolver is misconfigured, corrupt, or referencing a non-existent gateway. Common causes include corrupted network router DNS tables, obsolete static DNS IPs in your network adapter, third-party firewall interference, or outdated browser host cache entries. This tutorial walks you through practical methods to correct your DNS configuration and restore connectivity.

Method 1: Flush DNS Cache and Reset Network Sockets via Command Prompt

Stale DNS entries stored in your operating system cache can create configuration deadlocks. Purging the resolver and resetting network sockets forces Windows to rebuild clean routing rules.

1. Press the Windows key, type cmd, and click Run as administrator.
2. In the terminal window, execute the following commands in order, pressing Enter after each:

   ipconfig /flushdns
   ipconfig /release
   ipconfig /renew
   netsh winsock reset
   netsh int ip reset

3. Once all commands finish, restart your computer to apply the socket reset cleanly.

Method 2: Change DNS Server Addresses to Google or Cloudflare Public DNS

If your router’s default ISP-assigned DNS server has suffered an outage or has an invalid subnet configuration, switching your adapter to trusted public DNS resolvers resolves domain queries instantly.

1. Press Windows + R, type ncpa.cpl, and press Enter to open Network Connections.
2. Right-click your active connection (Wi-Fi or Ethernet) and select Properties.
3. Double-click Internet Protocol Version 4 (TCP/IPv4).
4. Select the radio button labelled Use the following DNS server addresses.
5. Configure reliable public DNS servers:
   • Cloudflare DNS: Preferred DNS: 1.1.1.1 | Alternate DNS: 1.0.0.1
   • Google Public DNS: Preferred DNS: 8.8.8.8 | Alternate DNS: 8.8.4.4
6. Check the box labelled Validate settings upon exit and click OK.
7. Click OK on the adapter properties window to save your settings.

Method 3: Clear Google Chrome Internal Host Resolver Cache

Google Chrome maintains its own independent DNS cache that sits on top of the operating system resolver. If Chrome caches a bad lookup, it will continue serving the error even after Windows network settings are corrected.

1. Open Google Chrome.
2. Type the following path into the address bar and press Enter:

   chrome://net-internals/#dns

3. Click the Clear host cache button.
4. Next, navigate to:

   chrome://net-internals/#sockets

5. Click Close idle sockets, followed by Flush socket pools.
6. Restart Chrome and test if web pages resolve normally.

Method 4: Configure Secure DNS (DNS over HTTPS) in Chrome

If your local router or network provider intercepts standard port 53 DNS packets, enabling encrypted DNS over HTTPS (DoH) inside Chrome bypasses local gateway configuration blocks.

1. In Chrome, click the three vertical dots menu in the top-right corner and select Settings.
2. Click Privacy and security in the left sidebar, then select Security.
3. Scroll down to the Advanced section.
4. Ensure Use secure DNS is toggled to On.
5. Select With (Custom) and choose Cloudflare (1.1.1.1) or Google (Public DNS) from the dropdown menu.
6. Reload your problematic tabs. Encrypted lookups will now travel over standard HTTPS port 443 directly to the chosen provider.

Chrome Bad Config DNS Diagnostics Reference Table

Refer to this reference matrix to isolate the cause of DNS probe errors:

Observed Condition	Probable Root Cause	Recommended Action
All websites return BAD_CONFIG simultaneously	Invalid DNS IP configured in network adapter	Change adapter IPv4 DNS to 1.1.1.1 and 1.0.0.1
Error occurs on one specific browser profile	Corrupted Chrome internal DNS socket pool	Clear host cache in chrome://net-internals/#dns
Error started immediately after VPN uninstall	Orphaned DNS split-tunneling adapter entries	Execute netsh winsock reset and restart PC
All devices on Wi-Fi show DNS errors	Home router DNS daemon crashed or hung	Power cycle router/modem (unplug for 60 seconds)
Error appears on corporate / school network	Local firewall blocking external public DNS ports	Revert adapter DNS to “Obtain DNS automatically”

Restarting the Windows DNS Client Service

In rare circumstances, the background Windows service responsible for caching queries (Dnscache) hangs. While Windows prevents manually stopping this service through services.msc, executing a registry reset rebinds it cleanly. Open Command Prompt as administrator and run net stop dnscache && net start dnscache. If access is denied by system permissions, restarting your PC achieves an identical clean service cycle.