DNS_PROBE_FINISHED_BAD_CONFIG means Chrome’s DNS probe detected that your network’s DNS configuration is invalid. Your computer’s DNS settings are misconfigured, pointing to DNS servers that are unreachable, returning errors, or not responding. This prevents Chrome from translating domain names into IP addresses, making all websites unreachable.
This error is different from DNS_PROBE_FINISHED_NXDOMAIN (the domain does not exist) and DNS_PROBE_FINISHED_NO_INTERNET (no network connection). The BAD_CONFIG variant specifically tells you that your DNS resolver settings need fixing. The good news: this is one of the easiest DNS errors to fix because it is entirely a client-side configuration problem.
What Causes DNS_PROBE_FINISHED_BAD_CONFIG
The most common cause is manually configured DNS server addresses that are incorrect or no longer active. This happens when you previously set custom DNS servers that have since changed their IP addresses, when a VPN modified your DNS settings and did not restore them after disconnecting, or when malware changed your DNS to redirect traffic through malicious servers that have been taken down.
Other causes include DHCP failures that provide incorrect DNS configuration from your router, corrupted network adapter settings after a driver update or system restore, conflicting DNS settings between IPv4 and IPv6 configurations, and router firmware bugs that hand out invalid DNS information to connected devices.
Fix 1: Switch to Google DNS or Cloudflare DNS
Replace your current DNS configuration with known-working public DNS servers. On Windows 10/11, go to Settings, Network & Internet, Change adapter options, right-click your active connection, select Properties, double-click Internet Protocol Version 4 (TCP/IPv4), select “Use the following DNS server addresses,” and enter 8.8.8.8 (preferred) and 8.8.4.4 (alternate). For Cloudflare, use 1.1.1.1 and 1.0.0.1. Click OK and close all dialogs. Also update IPv6 DNS: double-click Internet Protocol Version 6 and enter 2001:4860:4860::8888 and 2001:4860:4860::8844 for Google DNS.
Fix 2: Flush DNS Cache
After changing DNS servers, flush all cached entries. Open Command Prompt as Administrator and run “ipconfig /flushdns” followed by “ipconfig /registerdns.” Also clear Chrome’s internal DNS cache: navigate to chrome://net-internals/#dns and click “Clear host cache.” Then go to chrome://net-internals/#sockets and click “Flush socket pools.” Restart Chrome completely.
Fix 3: Reset Network Adapter
A corrupted adapter configuration can override your DNS settings. Open Command Prompt as Administrator and run: “netsh winsock reset” then “netsh int ip reset” then “ipconfig /release” then “ipconfig /renew.” Restart your computer after all commands. On Windows 10/11, you can also use the built-in network reset: go to Settings, Network & Internet, Advanced network settings, Network reset.
Fix 4: Restart Your Router
If DHCP is providing bad DNS configuration, your router may be the source. Power off your router completely (unplug from power), wait 30 seconds, then plug it back in and wait for it to fully boot. Once connected, check if the error is resolved. If your router has custom DNS settings configured in its admin panel, verify they point to valid DNS servers. Access your router admin at 192.168.1.1 or 192.168.0.1 (check the label on your router for the exact address).
Fix 5: Set DNS to Automatic
If manual DNS settings are causing the problem, switch to automatic DNS from your ISP. Go to your network adapter properties, double-click Internet Protocol Version 4, and select “Obtain DNS server address automatically.” Do the same for IPv6. This tells your computer to use whatever DNS servers your router provides via DHCP. While ISP DNS is often slower than Google or Cloudflare, it eliminates configuration errors.
Fix 6: Disable IPv6 Temporarily
Conflicting IPv6 DNS settings can cause BAD_CONFIG even when IPv4 DNS is correct. In your network adapter properties, uncheck “Internet Protocol Version 6 (TCP/IPv6)” temporarily. If the error resolves, the issue is with your IPv6 DNS configuration. Either set correct IPv6 DNS servers or leave IPv6 disabled if your network does not require it. Most home networks function perfectly with IPv4 only.
Frequently Asked Questions
Does DNS_PROBE_FINISHED_BAD_CONFIG affect all devices on my network?
It depends on the cause. If the problem is your router providing bad DNS via DHCP, all devices on the network are affected. If the problem is manual DNS settings on one specific computer, only that device is affected. Check another device on the same network to determine whether the issue is device-specific or network-wide.
Can DNS_PROBE_FINISHED_BAD_CONFIG be caused by malware?
Yes. DNS-hijacking malware changes your DNS settings to redirect traffic through malicious servers. When those malicious servers are taken offline, your DNS configuration points to dead servers, triggering BAD_CONFIG. Run a full antivirus scan and verify your DNS settings match known-good values (Google: 8.8.8.8, Cloudflare: 1.1.1.1) after cleaning.
Why does this error appear after a Windows update?
Windows updates occasionally reset network adapter settings or overwrite custom DNS configurations. After any major Windows update, verify your DNS settings are still correct. Go to your network adapter properties and confirm the DNS server addresses are set to your preferred values (or set to automatic if you were using DHCP).
