Site icon Software Test Tips

8 Fixes for “DNS_PROBE_FINISHED_BAD_CONFIG” in Chrome

8 Fixes for “DNS_PROBE_FINISHED_BAD_CONFIG” in Chrome

DNS_PROBE_FINISHED_BAD_CONFIG Error?

I was browsing on the internet, and suddenly the “dns_probe_finished_bad_config” error appeared. I learned from many sources that this error happens when my device’s DNS server can’t resolve a website address that I have tried to visit. In many cases, this is due to an undiagnosed fault with your device’s DNS settings.

It could be because a DNS server is down or no longer responding. It may also be possible your device’s network settings are incorrect. Chrome, for example, will be unable to load websites if the incorrect DNS server settings are added. It results in a dns_probe_finished_bad_config error (or similar).

DNS_probe_finished_bad_config error problem is platform agnostic. The error appears in Chrome on any supported device (including Mozilla Firefox or Mac). Unfortunately, there isn’t a single cause for this warning. You may take several typical troubleshooting methods to remedy the problem that should work for most customers.

Means to Fix “DNS_PROBE_FINISHED_BAD_CONFIG” Error Code?

When I modify “Network Connection,” my computer can utilize the DNS address in my router or modem. It is an Internet service provider DNS. I usually advocate using public DNS servers, which you can find in this guide. They are the most popular and have a 99.9% uptime.

You can also look at many alternatives to fix dns_probe_finished_bad_config error.

1. Delete the Cache in Your Browser

While this is unlikely to cause the DNS error, it doesn’t harm to rule it out. You might wish to start using a different browser from the one you’re currently using to visit the website. 

If that doesn’t work, the next logical step is to clear the cache and temporary files of the problematic browser.

2. Change The Preferred DNS Server Manually 

Fix dns_probe_finished_bad_config error message if it still appears in your browser. The next step is to change your DNS settings. Default by your ISP assigns DNS servers.

You can, however, temporarily use a public DNS server like Google.

3. Flush the DNS Cache

If your DNS has recently been changed, whether deliberately or mistakenly. Your system may be attempting to connect to the network using the local cache.

Understandably, you’d get to fix dns_probe_finished_bad_config warning if this is the case.

As a result, cleaning your DNS cache, as well as releasing and renewing your IP address, are the next steps to take. If you’re using Windows 10 or 7, you can use the Command Prompt app to achieve this.

On Mac, add the following DNS server addresses.

4. Restart your router

Even if your router is connected correctly, a fast reboot may be required to reset the IP settings. As a result, the initial step you should follow is to restart your router.

Simply hold down the power button to do so. Turn it back on after leaving it off for at least one minute. You might wish to reset your computer while it’s resuming.

Connect to your LAN network or Wi-Fi and try browsing the website again after both devices have been turned back on. If the error still appears, it is time to try to fix dns_probe_finished_bad_config with the following approach.

5. Disable Your Antivirus

Antivirus software, windows defender security center, and VPNs can sometimes conflict with network connections, which is a common problem. They can, in particular, cause problems with your DNS servers.

If the “Fix dns_probe_finished_bad_config” error persists, the next step is to temporarily disable your antivirus software and firewall software.

Here’s a Windows-based example.

6. Install the latest network drivers

Suppose you’re still not able to get rid of getting the dns_probe_finished_bad_config error message. We do, however, have one more option, i.e., updating your network drivers.

Network drivers that are outdated or faulty can cause a range of problems, including DNS and network outages. The necessary updates are usually handled through Windows Updates. You can, however, double-check to see if you can manually upgrade to the latest version.

7. Disable Website Blocking Software

If you’re using website blockers or a PN app, turn them off for a while to see if this solves the dns_probe_finished_bad_config error.

After turning off their website filters, some users confirmed that the DNS issues had vanished in the operating system. Please test this solution to see if it also works for you.

For Google Chrome, follow the below procedure.

8. Delete the Temporary Files

The majority of browsers save temporary files on your device for later use. If any file is corrupted, the dns_probe_finished_bad_config error may occur.

Conclusion

To repair a dns_probe_finished_bad_config error in Google Chrome, follow the steps above. You may need to try switching to another browser or resetting Google Chrome to its default settings to investigate further.

The Dns_probe_finished_bad_config is quite simple to fix. If you’re having trouble with the dns_probe_finished_bad_config mistake, use one of the above solutions to fix it.

Frequently Asked Questions

What does bad config mean?

Bad System Config Info is a typical Windows bug check issue produced by a malfunction of the system and registry files and the Boot Configuration Data (BCD) file. Incompatible hardware can also trigger DNS errors.

What is internet protocol version 4/6? 

IPv4 and IPv6 are both binary integers that represent IP addresses. IPv6 vs. IPv4, IPv4 is a 32-bit binary number, whereas IPv6 is a 128-bit binary number. Periods divide IPv4 addresses, while colons divide IPv6 lessons. Both of these methods are used to identify machines that are connected to a network.

Recommended Articles

Exit mobile version