Although not common, it’s not unusual to see DNS_PROBE_FINISHED_BAD_CONFIG error while browsing the Internet. In many cases, it has to do with the website itself or long-running browsing sessions, and refreshing the page gets rid of it. But what if it doesn’t, and waiting a few minutes produces no results either? It requires a deeper analysis, obviously. Fortunately, we’ve prepared more than a dozen potential solutions, and one of them will work. So, let’s get into how to fix DNS_PROBE_FINISHED_BAD_CONFIG error.
What is DNS_PROBE_FINISHED_BAD_CONFIG error?
DNS_PROBE_FINISHED_BAD_CONFIG error is an error displayed on Chrome, Edge, Firefox, Safari, Opera, and Internet Explorer, regardless of the operating system. Its cause varies but usually has to do with a network configuration changed by an app or program. In rare cases, it can be caused by faulty network equipment, whether yours or the one belonging to your ISP (Internet Server Provider).
1. Try these methods before you proceed
Before you go any further, go through the methods for fixing the DNS_PROBE_FINISHED_NO_INTERNET error, since the two errors have similar causes. When you exhaust those options, continue with the methods below.
2. Fix DNS_PROBE_FINISHED_BAD_CONFIG error with Chrome Cleanup Tool
By now, you should’ve eliminated the majority of the reasons DNS_PROBE_FINISHED_BAD_CONFIG error appears. It’s time to look at external causes such as adware, malware, spyware, hacking via backdoor access, etc. So, if you’re a Google Chrome user, run its Cleanup Tool like this:
- In the top right corner, click on More (3 vertical dots).
- From the drop-down menu select Settings.
- Expand the list by clicking on Advanced.
- Find the Reset and cleanup section, then click on Clean up computer.
- Choose whether to send analytics to Google, then click on the Find button.
- If it finds any malicious software, Chrome will ask you to click on Remove.
- Tip. You might have to restart your computer, so save your work.
3. Disable browser extensions/add-on
The next step to finding a culprit for the DNS_PROBE_FINISHED_BAD_CONFIG error is to disable browser extensions (Chrome) or add-ons (Firefox). Here’s how to do toggle off browser add-ons or extensions:
- Chrome: Click on More, select More Tools, then, when it expands, Extensions.
- Firefox: Click on the menu button (sandwich icon), select Add-ons, then Extensions.
Which ones should I disable?
4. Reset browser settings
If none of the browser extensions were a source of the DNS_PROBE_FINISHED_BAD_CONFIG error, it’s hard to pinpoint what is, and where it’s located. So, you can make a radical step and restore browser settings to default like this:
Click on More once again, and then:
- Go to Settings, then expand the list by clicking on Advanced.
- Now, based on the operating system, do this:
- Windows. Go to Reset and cleanup again, then select Reset settings. Confirm by clicking on Reset settings again.
- Mac, Linux, Chromebook. Find the Reset Settings section. Select Restore settings to their original defaults, then confirm by clicking on Reset settings.
Click on the menu button again, and then:
- At the bottom, click on Help.
- When a new menu opens, select Troubleshooting Information.
- In the upper right corner, click on Refresh Firefox…
- When prompted, click on Refresh Firefox.
- After the process is complete, click on Finish.
5. Fix DNS_PROBE_FINISHED_BAD_CONFIG error via VPN
Before you decide to reinstall your operating system, we have a final suggestion. Why not hide your identity and location as a solution to the DNS_PROBE_FINISHED_BAD_CONFIG error? In other words, get access to a VPN (Virtual Private Network) or create your own. If it works, you can run a VPN continuously and use split tunneling to check when to disable it. Alternatively, exchange your default Internet browser for other browsers with a VPN. On the other hand, if you’re already using a VPN, disable it shortly or change your VPN service provider.