DNS_PROBE_FINISHED_BAD_CONFIG Error – Finding the Causes and Fixes!

Jack

By Jack

Update on

DNS_PROBE_FINISHED_BAD_CONFIG

DNS_PROBE_FINISHED_BAD_CONFIG is a common network connection error faced by any user while opening any website on any browser.

This DNS error points out faulty DNS configurations of the system that prevents it from connecting to any internet. It is this error that we are going to analyze for you and also give the best solutions to fix it.

dns_probe_finished_bad_config

Why Does the DNS_PROBE_FINISHED_BAD_CONFIG Appear on Your Screen?

Let us make you aware of certain factors that can cause this DNS_PROBE_FINISHED_BAD_CONFIG error in your PC:

  • A DNS can be defined as a particular IP address the network assigns to the PC. The failure of the network in translating this IP address because of any faulty configuration causes the DNS error while you try to open any webpage.
  • Any third-party unauthorized application might be trying to meddle with your network settings associated with the router.
  • The network settings of the system might have been changed by you unknowingly.
  • Any browser plug-in might have hijacked your system’s IP address or DNS address. VPN apps can be one example of changing the location, hiding your identity, and causing DNS errors.

PS: here are the top solutions for the errors like ERR_ADDRESS_UNREACHABLE on Google Chrome for your reference.

Does the Error Happen in Any Specific Browser?

The dns_probe_finished_bad_config error does not happen on any particular website; thus, you can expect it to occur while opening any website.

Also, any specific browser doesn’t suffer from it. This error happens over Chrome, Safari, Firefox, Opera, etc.

The main basis of the error is the network, and any problem will become the causal factor. This also means that you might face the issue while opening any website on any internet browser. Remember that the same network is accessed while opening any website or browser.

You might think about why the error happens most frequently with Chrome users. Well, it is because the Google Chrome browser is the most used one by people worldwide, which will give the highest number of issues and complaints related to Chrome only.

The DNS_PROBE_FINISHED_BAD_CONFIG error has also been reported by several Android users, which was mainly the result of faulty router configurations.

Also, click to figure out the best VPN – Speedify Review.

What Can Fix the DNS_PROBE_FINISHED_BAD_CONFIG Error?

The occurrence of this error disables the users from running a lot of system functions and primarily from accessing any website. You might have tried changing the browser that you have been using and yet not been able to remove the DNS error.

If you cannot see any way of getting out of this situation, let us help you with that, as we provide some of the best solutions here in this section of the article.

By the way, for people experiencing the Windows 0xc1900101 error, here are the top solutions for you.

Try Restarting the Router

This can be the primary method to try as it is simple and may remove the error if minor faults are causing it.

Deciding to restart the router will help you eliminate the error in all devices, be it Windows PC, macOS, or an Android Smartphone.

All it takes to restart the router is turning off the power button. Wait for some time, and then you can turn it on.

Once done, you must restart the PC or any other device.

After doing the same process with both devices, establish the network connection again, either with the WiFi provider or the LAN cable.

The method should have successfully troubleshot the device for any problem. You can try opening any website, and the access will be free of issues this time.

However, if the method fails to work out for you, the issue is something else, and move ahead with the other fixes.

Empty the Browser Cache

A full cache with corrupted and old files can become the major cause behind the dns_probe_finished_bad_config error.

A good solution to try in such a situation is to clear the cache of the browser you are using and disable the cookies.

Whether you use any browser like Google Chrome or Firefox, it is a simple method.

Follow the general steps given below to perform the method for any browser:

  • Open the particular browser that you have.
  • Go to Settings of the browser.
  • Navigate and search for the option Browsing data, browser History, or other similar things.
  • The option for Opera, Firefox, and Chrome browser would be Browsing data.
  • Open it, and you can delete all the cookies and cache data here.
  • Tick mark the box against the option related to cookies and hosted application data. Select a time range as well.
Empty the browser cache

Most cases involving the DNS error bugging them have been proven to get solved by this method. In case it doesn’t, follow some other solution.

Delete the Temporary Files

A feature of most browsers allows the storage of some kinds of temporary files that are there to facilitate quick access later and also enhance the browsing experience of the user.

Now, these files can become the potential culprit behind the DNS error if they go corrupt for any reason.

In the Windows OS, these temporary files can be found in a directory named ‘Temp.’ You can gain access to it if you follow the simple steps that we give below.

  • Press the keys Windows + R together.
  • You can also launch the Run dialogue box by going into the Start menu of Windows and then opening the All Programs option.
  • When the Run box emerges up, enter the command %temp%.
  • Click Enter now.
  • Now you can view all the temporary files that are stored on the PC that you are using.
Delete the temporary files

The macOS has such files stored at a different location, and to find that out; you can follow these steps:

  • Press the keys G + CMD + Shift at the same time.
  • This will launch a dialogue box.
  • Enter the command ~/Library/Caches into the text space.
  • All this, when done successfully, will enable you to view the temporary files that were taking up space on your Mac PC.
Delete the temporary files

Now what you need to do after finding all the temporary files stored on the specific PC you are a user of is select all of them and delete them.

Once upon getting rid of all these files, you can expect the resolution of the dns_probe_finished_bad_config problem.

Reset Your Chrome Browser

This step is only meant for users of the Google Chrome browser. If you are a user of other browsers like Opera or Firefox, then you may need to contact their specific support centers, as they will be able to tell you the method for resetting those browsers.

Performing a browser reset changes its settings, which may prove helpful in removing the error. Let us tell you how to do it:

  • Launch the browser.
  • Open Settings.
  • Find and open the option of Show Advanced Settings.
  • Click on it and expand its menu.
  • You will see an option of Reset Settings over here present at the bottom.
  • Click on it, and this will reset the browser.
Reset your Chrome browser

Refresh the DNS and Change the IP Address

This may be the last option that you will have to resort to, but it can fix every related issue to the DNS since we are adopting a complete cleanout approach with this method.

You can flush out the DNS first to proceed with the method. This method will reset the DNS and performs an overall fixing of the configuration of the DNS.

Follow the steps below to do so:

  • Press the keys Windows + R together to launch the Run dialogue box.
  • You can do the same by opening the Start menu and clicking the All Programs option.
  • Into the box, enter the command cmd. Click Enter to open the Prompt Command.
cmd
  • Now we have to enter certain commands one by one.
  • Enter ipconfig /flushdns. Hit OK.
Refresh the DNS and change the IP Address
  • Enter ipconfig /renew. Hit OK.
Refresh the DNS and change the IP Address
  • Enter ipconfig /release. Hit OK.
Refresh the DNS and change the IP Address
  • Enter ipconfig /all. Hit OK.
  • Lastly, restart the PC.

Open the browser on it and try opening the websites again. See if the DNS error is resolved.

Method for Fixing the DNS_PROBE_FINISHED_BAD_CONFIG Error in Windows 7/8/10

By default, the computer systems are configured to run using the DNS associated with your modem or router.

The Internet provider sets this DNS unless you manually change it.

We suggest you use the Public DNS servers as they give better functioning and remain mostly active with an uptime of around 99%.

If all this sounds too techie, don’t worry; just follow the steps we give you.

For manually find the corrupt files and deleting them, follow the given steps below:

  • Press the keys Windows + R together.
  • In the Run dialogue box that launches up, enter the command cmd. Hit OK.
  • A black Command Prompt will open up now. Enter the command given below. Hit Enter.

ipconfig /flushdns

Method for fixing the dns_probe_finished_bad_config error

The DNS cache will be removed, which becomes the potential reason for DNS malfunctioning.

It happens due to the system basing upon the old local cache for taking you to open the websites that you want to view.

  • Press the keys Windows + R.
  • Enter the command ncpa.cpl. Hit OK.
ncpa.cpl
  • The window of network connections will open up now.
  • You have to modify the DNS settings here to update them.
  • Find the network adapter that is connected to the system. Hit a right-click over it. Select Properties.
Method for fixing the dns_probe_finished_bad_config error
  • Inside this Properties windows pane, select the option of Internet Protocol Version 4 (TCP/IPv4). Make sure that the option gets highlighted and turns grey. Open the Properties again.
Method for fixing the dns_probe_finished_bad_config error
  • Tick mark the box against the option ‘Use the following DNS server addresses.’ Now enter the given options for the Preferred DNS Server and the Alternate DNS Server, respectively.

8.8.8.8

8.8.4.4

Method for fixing the dns_probe_finished_bad_config error
  • Hit the button, OK. Close all the windows.
  • If the dns_probe_finished_bad_config error persists and you fail to use the internet, try some other DNS addresses we give and see if the problem gets resolved.

Preferred DNS: 208.67.222.222

Alternate DNS: 208.67.220.220

Method for fixing the dns_probe_finished_bad_config error

If you think a third-party tool can do all of this better for you, then you can take help from the software Reimage Plus, which aims to scan and find corrupt files and help you delete them easily.

FAQs

Q1: What is DNS_PROBE_FINISHED_BAD_CONFIG?

A1: It’s an error that occurs when your browser can’t establish a connection with a website’s server, usually due to issues with DNS settings or the internet connection.

Q2: What causes DNS_PROBE_FINISHED_BAD_CONFIG?

A2: This error can be caused by problems with your DNS settings, internet connection, network configuration, firewall settings, or even your ISP.

Q3: How does DNS_PROBE_FINISHED_BAD_CONFIG affect my internet usage?

A3: When this error occurs, it prevents you from accessing certain websites, acting as a roadblock in your internet journey.

Q4: How can I resolve DNS_PROBE_FINISHED_BAD_CONFIG?

A4: Several solutions can be employed, including restarting your device, clearing your DNS cache, changing your DNS server, resetting your router, checking your firewall and antivirus software, or contacting your ISP.

Q5: What if none of the solutions work?

A5: If you’ve tried all the suggested solutions and the issue persists, it’s best to contact your ISP. They may have more information or specific solutions to help you.

Conclusion

This was all about the dns_probe_finished_bad_config error, why it occurs, and what can be done to fix it.

We hope our efforts will prove helpful to you and that the methods are the best so you won’t need to go and look for solutions anywhere else.

Jack
Jack

Ten years of experience in information and computer technology. Passionate about electronic devices, smartphones, computers, and modern technology.

THERE’S MORE TO READ.