How to Fix DNS Probe Finished Bad Config in Chrome

If you see “DNS_PROBE_FINISHED_BAD_CONFIG” in Chrome, your browser can’t reach the internet because the DNS (Domain Name System) settings on your device are wrong or blocked. This guide walks you through the most effective fixes, from flushing the DNS cache to changing your DNS server, and covers what to do if the problem persists.

What You’ll Need

• Administrator access to your computer (to run commands and change network settings).
• Your Wi-Fi password (if you need to reconnect to your network).
• A few minutes of patience—some steps require a restart.

Step-by-Step

1. Restart your router and computer. Unplug your router for 30 seconds, plug it back in, and wait for it to fully boot. Then restart your computer. This clears temporary glitches that often cause the error.
2. Flush the DNS cache. Open Command Prompt (Windows) or Terminal (Mac) as administrator. Type ipconfig /flushdns on Windows or sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder on Mac, then press Enter. This clears old, incorrect DNS entries.
3. Reset the network stack. In the same Command Prompt (Windows), run these commands one by one, pressing Enter after each: ipconfig /release, ipconfig /renew, netsh winsock reset, netsh int ip reset. Restart your computer afterward.
4. Change your DNS server. Go to your network adapter settings (Control Panel > Network and Sharing Center > Change adapter settings on Windows, or System Preferences > Network on Mac). Right-click your active connection and select Properties. Choose Internet Protocol Version 4 (TCP/IPv4), then select “Use the following DNS server addresses.” Enter 8.8.8.8 and 8.8.4.4 (Google DNS) or 1.1.1.1 and 1.0.0.1 (Cloudflare). Save and restart Chrome.
5. Disable Chrome’s built-in DNS feature. In Chrome, go to Settings > Privacy and security > Security. Turn off “Use secure DNS” (or “DNS over HTTPS”) and try again. This resolves conflicts with certain networks.
6. Check your proxy settings. In Windows, go to Settings > Network & Internet > Proxy and ensure “Use a proxy server” is off (unless you actually use one). On Mac, check System Preferences > Network > Advanced > Proxies. Malware or leftover VPN settings can cause this error.
7. Run a malware scan. Use Windows Defender or a trusted antivirus to scan your system. Some malware changes DNS settings without your knowledge.
8. Reset Chrome flags. Type chrome://flags in the address bar, press Enter, and click “Reset all” at the top right. This reverts any experimental settings that might interfere.

Common Mistakes

• Skipping the router restart. Many users only restart their computer, but the router may hold the bad DNS cache. Always restart both.
• Entering DNS addresses incorrectly. A typo like 8.8.8.8 vs 8.8.8.9 will not work. Double-check each number.
• Not running commands as administrator. The netsh and ipconfig commands require admin rights; otherwise, they fail silently.
• Forgetting to reconnect after changing DNS. After changing DNS settings, you may need to disconnect and reconnect to your Wi-Fi for the change to take effect.

Tips

• Use a reliable public DNS. Google (8.8.8.8) and Cloudflare (1.1.1.1) are fast and dependable. You can also use your ISP’s DNS, but public ones often resolve errors faster.
• Check if the issue is site-specific. Try visiting a different website. If only one site fails, the problem is likely with that site’s server, not your DNS.
• Use Chrome’s built-in network diagnostics. When the error appears, click the “Network” button on the error page. Chrome will run a diagnostic and may suggest a fix.
• Keep your OS and Chrome updated. Outdated software can have bugs that cause DNS issues. Regular updates prevent many problems.

Troubleshooting

If the error persists after trying all the steps above, consider the following:

• Try a different browser. If Firefox or Edge works, the issue is Chrome-specific. Try reinstalling Chrome or resetting its settings to default (Settings > Advanced > Reset and clean up > Restore settings to their original defaults).
• Check your firewall or antivirus. Some security software may block DNS requests. Temporarily disable them (if safe) to test, then re-enable and whitelist Chrome.
• Contact your ISP. Sometimes the ISP’s DNS servers are down. Call them and ask if there are known outages.
• Try a different network. Connect to a mobile hotspot or a friend’s Wi-Fi. If the error disappears, your home network or router is the culprit.
• Use Chrome’s clean up tool. Go to Chrome settings > Advanced > Reset and clean up > Clean up computer. This removes suspicious software that might alter DNS.

Frequently Asked Questions

What does DNS_PROBE_FINISHED_BAD_CONFIG mean?

It means Chrome sent a DNS query but received no valid response, usually because your DNS settings are incorrect, the DNS server is unreachable, or a firewall is blocking it.

Will changing my DNS server affect my internet speed?

It can. A faster DNS server (like Google or Cloudflare) can speed up the time it takes to load a website, but your overall bandwidth (download/upload) remains the same.

Is this error a sign of malware?

Not necessarily, but malware can change DNS settings to redirect you. If the error appears suddenly and you haven’t changed settings, a malware scan is a good precaution.

Why does this error happen on my phone too?

If the error occurs on all devices, the problem is likely your router or ISP. Restarting the router or changing its DNS settings (in the router admin panel) can help.

Can I fix this without admin access?

Most fixes require admin rights. If you’re on a work or school computer, contact your IT department—they can adjust network settings for you.

How often should I flush my DNS cache?

Only when you have connection issues. Flushing daily is unnecessary and can slightly slow down browsing because your device has to re-learn DNS addresses.

Related

• Fix Registry Editor Cannot Import Error
• Agentic QA: How It Changes Software Testing
• How to Open a New Tab in Chrome