By /

DNS_PROBE_FINISHED_BAD_CONFIG Error – Complete Fix Guide (2026)

Table of Contents

Hub: Windows 11 Troubleshooting Hub

Quick Answer
A DNS_PROBE_FINISHED_BAD_CONFIG Error indicates that your browser cannot resolve a domain name due to a DNS configuration issue. To fix it, restart your router and computer, flush the DNS cache, change your DNS server to Google (8.8.8.8) or Cloudflare (1.1.1.1), reset the TCP/IP stack, and check proxy settings. If the error persists, disable IPv6, clear browser cache, or check the hosts file. For more networking troubleshooting, visit our Windows 11 Troubleshooting Hub.

Why DNS_PROBE_FINISHED_BAD_CONFIG Error Happens

A DNS_PROBE_FINISHED_BAD_CONFIG Error occurs when your browser cannot resolve a domain name to its IP address because of a DNS configuration problem. This error is specific to Google Chrome and other Chromium-based browsers, indicating that the DNS probe completed but found a bad configuration. For official documentation, refer to the Google Chrome net-error-codes documentation.

The DNS_PROBE_FINISHED_BAD_CONFIG Error typically appears when your DNS settings are incorrect, the DNS cache is corrupted, or your network configuration is misaligned. This error is similar to other DNS errors like DNS Server Not Responding in Windows 11 and Windows Error 0x80072ee7, but it specifically indicates a bad configuration rather than a server timeout. Common triggers include incorrect DNS server addresses, corrupted DNS cache, proxy server interference, IPv6 issues, or a misconfigured hosts file.

Before diving into fixes, ensure you have administrator privileges on your PC. If you are on a corporate network, contact your IT administrator before changing DNS settings. For a broader overview of network errors, see our Windows 11 Troubleshooting Hub.

⚠️ Warning: A DNS_PROBE_FINISHED_BAD_CONFIG Error can occur due to malware that modifies DNS settings. If the error persists, run a malware scan.

1. Restart Your Router and Computer

The simplest fix for a DNS_PROBE_FINISHED_BAD_CONFIG Error is restarting your router and computer. This clears temporary network glitches and refreshes your IP configuration.

  1. Restart your computer.
  2. Power off your modem and router. Unplug them from power.
  3. Wait 30 seconds, then plug them back in.
  4. Wait for all lights to stabilize, then restart your PC.
  5. Open Chrome and try loading the website again.

✅ Expected Result: A restart often resolves the DNS_PROBE_FINISHED_BAD_CONFIG Error immediately. If not, proceed to the next method.

2. Flush DNS Cache

Corrupted DNS cache can cause the DNS_PROBE_FINISHED_BAD_CONFIG Error. Flushing the DNS cache forces your system to retrieve fresh DNS records.

  1. Open Command Prompt as Administrator.
  2. Run the following command:
    ipconfig /flushdns
  3. Wait for the confirmation message.
  4. Restart your browser and try loading the website again.

💡 Quick Tip: You can also clear Chrome’s internal DNS cache by typing chrome://net-internals/#dns in the address bar and clicking “Clear host cache.”

3. Change DNS Server Settings

Your ISP’s DNS servers may be slow or misconfigured, causing the DNS_PROBE_FINISHED_BAD_CONFIG Error. Switching to public DNS servers like Google DNS or Cloudflare can resolve the issue.

  1. Open Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active network connection and select Properties.
  3. Select Internet Protocol Version 4 (TCP/IPv4) and click Properties.
  4. Select “Use the following DNS server addresses” and enter:
    • Preferred DNS server: 8.8.8.8 (Google DNS)
    • Alternate DNS server: 8.8.4.4 (Google DNS)
  5. Alternatively, use Cloudflare DNS: 1.1.1.1 and 1.0.0.1.
  6. Click OK and restart your PC.

🔁 Alternative Solution: You can also change DNS settings in Chrome by visiting chrome://settings/security and configuring “Use secure DNS.”

4. Reset TCP/IP Stack

A corrupted TCP/IP stack can cause the DNS_PROBE_FINISHED_BAD_CONFIG Error. Resetting it restores default network settings.

  1. Open Command Prompt as Administrator.
  2. Run the following commands in sequence:
    netsh int ip reset
netsh winsock reset
  3. Restart your PC.
  4. Try loading the website again.

✅ Expected Result: Resetting the TCP/IP stack often resolves persistent DNS_PROBE_FINISHED_BAD_CONFIG Error issues.

5. Check Proxy Settings

Proxy server settings can interfere with DNS resolution and cause the DNS_PROBE_FINISHED_BAD_CONFIG Error. Disabling proxy settings can resolve the issue.

  1. Open Settings > Network & Internet > Proxy.
  2. Ensure “Use a proxy server” is turned Off.
  3. In Chrome, go to chrome://settings/system and ensure “Open your computer’s proxy settings” is not enabled.
  4. If you are on a corporate network, contact your IT administrator for correct proxy settings.

❌ Common Mistake: Forgetting to disable proxy settings after testing. If the error resolves, you may need to configure the proxy correctly rather than disabling it permanently.

6. Disable IPv6

IPv6 can sometimes cause the DNS_PROBE_FINISHED_BAD_CONFIG Error if your network does not support it properly. Disabling IPv6 can help.

  1. Open Control Panel > Network and Sharing Center > Change adapter settings.
  2. Right-click your active network connection and select Properties.
  3. Uncheck Internet Protocol Version 6 (TCP/IPv6).
  4. Click OK and restart your PC.
  5. Test if the error is resolved.

🔁 Alternative Solution: If you need IPv6 for other services, try enabling it again after confirming your network supports it.

7. Clear Browser Cache and Cookies

Corrupted browser cache can trigger the DNS_PROBE_FINISHED_BAD_CONFIG Error. Clearing the cache and cookies can resolve it.

  1. Open Chrome and press Ctrl + Shift + Delete.
  2. Select “All time” for time range.
  3. Check “Cookies and other site data” and “Cached images and files”.
  4. Click Clear data.
  5. Restart Chrome and try loading the website again.

💡 Quick Tip: You can also clear DNS cache in Chrome by visiting chrome://net-internals/#dns and clicking “Clear host cache.”

8. Check Hosts File

Incorrect entries in the hosts file can block domain resolution and cause the DNS_PROBE_FINISHED_BAD_CONFIG Error. Check for any entries that may be redirecting legitimate domains.

  1. Navigate to C:\Windows\System32\drivers\etc.
  2. Open the hosts file with Notepad (as administrator).
  3. Look for entries that may be blocking domains (e.g., entries with 127.0.0.1 or 0.0.0.0 followed by a domain name).
  4. If you find suspicious entries, remove or comment them out with a #.
  5. Save the file and restart your PC.

⚠️ Warning: Do not delete the default entries in the hosts file (e.g., ::1 localhost, 127.0.0.1 localhost). Only remove custom entries that may be causing issues.

9. Advanced Troubleshooting

If the error persists, try these advanced solutions.

Reset Chrome Settings

Reset Chrome to default settings: go to chrome://settings/reset and click “Restore settings to their original defaults”.

Check for Malware

Malware can modify DNS settings. Run a full scan with Windows Defender Offline. For detailed steps, see How to Scan Malware Windows 11.

Perform a Clean Boot

A clean boot eliminates software conflicts. Press Win + R, type msconfig, go to Services, check “Hide all Microsoft services,” click Disable all, disable startup items in Task Manager, restart, and test.

Use the Windows Network Troubleshooter

Run the built-in network troubleshooter: Settings > System > Troubleshoot > Other troubleshooters > Internet Connections > Run.

Flush Chrome DNS Cache

Visit chrome://net-internals/#dns and click “Clear host cache”. Then visit chrome://net-internals/#sockets and click “Close idle sockets” and “Flush socket pools”.

Check for DNS Leaks

If using a VPN, check for DNS leaks using online tools. For more, see How to Fix DNS Leak Test.

For more networking troubleshooting, explore our Windows 11 Troubleshooting Hub.

Conclusion

A DNS_PROBE_FINISHED_BAD_CONFIG Error is a common DNS issue that can be fixed by restarting your router, flushing DNS cache, changing DNS servers, resetting TCP/IP, and checking proxy settings. If the error persists, disable IPv6, clear browser cache, check the hosts file, or perform advanced troubleshooting like resetting Chrome or scanning for malware. By following these steps, you can resolve the error and restore your internet connectivity.

Regular system maintenance, such as keeping your network drivers updated and periodically flushing DNS cache, can prevent the DNS_PROBE_FINISHED_BAD_CONFIG Error from recurring. For more Windows and browser troubleshooting, explore our Windows 11 Troubleshooting Hub and check out related articles on DNS Server Not Responding, Chrome ERR_CONNECTION_TIMED_OUT, and Your Connection is Not Private.

Related Guides

FAQ

What causes DNS_PROBE_FINISHED_BAD_CONFIG Error?

A DNS_PROBE_FINISHED_BAD_CONFIG Error is caused by incorrect DNS settings, corrupted DNS cache, proxy server interference, IPv6 issues, or a misconfigured hosts file.

How do I fix DNS_PROBE_FINISHED_BAD_CONFIG Error?

Restart your router and computer, flush DNS cache, change DNS servers to Google (8.8.8.8), reset TCP/IP stack, check proxy settings, and clear browser cache.

Can changing DNS servers fix this error?

Yes, switching to public DNS servers like Google DNS (8.8.8.8) or Cloudflare DNS (1.1.1.1) often resolves the DNS_PROBE_FINISHED_BAD_CONFIG Error.

Is DNS_PROBE_FINISHED_BAD_CONFIG a virus?

No, it is a DNS configuration error, not a virus. However, malware can modify DNS settings and cause this error.

How do I flush DNS cache in Windows 11?

Open Command Prompt as Administrator and run ipconfig /flushdns.

Can proxy settings cause DNS_PROBE_FINISHED_BAD_CONFIG?

Yes, proxy server settings can interfere with DNS resolution and cause this error. Disable proxy settings to test.

Does clearing browser cache fix this error?

Yes, clearing browser cache and cookies can resolve the DNS_PROBE_FINISHED_BAD_CONFIG Error.

What is the hosts file and how does it affect DNS?

The hosts file is a local DNS mapping file. Incorrect entries can block domain resolution and cause this error.

Can IPv6 cause DNS_PROBE_FINISHED_BAD_CONFIG?

Yes, IPv6 can cause this error if your network does not support it properly. Disabling IPv6 can resolve the issue.

What should I do if the error persists after all fixes?

If the error persists, run a malware scan, reset Chrome settings, perform a clean boot, or contact your network administrator.

HowToFixPro Editorial Team

We’re a team of system administrators, technical writers, and platform specialists who genuinely enjoy solving the problems most users find frustrating. From persistent Windows errors and Android sync failures to browser crashes and network drops — we’ve seen it all, and we document every fix properly. Our guides are built on official documentation, direct testing, and real troubleshooting experience. No filler, no guesswork — just reliable, step-by-step solutions you can trust.

Scroll to Top