Dns probe finished bad config windows 10

When you’re browsing online, encountering an error message that prevents you from accessing a website is incredibly frustrating. One such error is the ‘DNS_PROBE_FINISHED_BAD_CONFIG’ message. It can occur regardless of your browser or Operating System.

If you run into this error when trying to open a site, don’t panic. It simply means that the Domain Name System (DNS) wasn’t able to resolve the IP address properly, which can happen for a variety of reasons.

Fortunately, as with most DNS-related issues, there are some simple solutions you can try to fix this problem.

In this article, we’ll explain what the DNS_PROBE_FINISHED_BAD_CONFIG error code means and some common causes of it. Then we’ll walk you through seven solutions for fixing it in Windows, macOS, Android, and Ubuntu.

Let’s get started!

What Is the DNS_PROBE_FINISHED_BAD_CONFIG Error?

To understand what this error means, it’s helpful to first get a general idea of the important role the DNS plays in helping users access websites. In a nutshell, the DNS directs traffic on the internet and is responsible for translating and connecting nameservers, URLs, and IP addresses with web servers.

All websites have unique IP addresses, such as 218.3.120.12. Rather than requiring you to memorize and enter the IP address any time you want to visit a website, the DNS makes it so you can use a more user-friendly domain name, such as kinsta.com.

When you input the URL into your browser, it begins the process known as DNS name resolution. This is where the DNS essentially looks up the URL/IP address and connects it with a web server. However, if for whatever reason the DNS is not able to successfully complete this process, it can return an error message instead.

DNS_PROBE_FINISHED_BAD_CONFIG is a network connection error that displays when there is a problem with the DNS configuration, which prevents it from connecting to a network. It is not specific to any one browser or system, meaning you could come across it in Google Chrome, Windows, or macOS, on an Android mobile device, etc.

Similar DNS Error Messages

A DNS error message occurs when your DNS or network settings are misconfigured. The DNS_PROB_FINISHED_BAD_CONFIG error is just one of them, and there are other similar messages you may run across.

For example, you might see the DNS_PROBE_FINISHED_NXDOMAIN error:

In this error message, “NXDOMAIN” stands for “Non-Existent Domain”. In other words, the domain name that was queried doesn’t exist.

Another similar DNS error is DNS_PROBE_FINISHED_NO_INTERNET:

This error message indicates that a problem occurred while establishing an internet connection, or that the connection was lost.

Any of the above DNS errors can vary depending on the browser you’re using. So your message might also include phrases such as:

• This web page is not available.
• This site can’t be reached.
• Safari can’t find the server.
• We’re having trouble finding the site/web page.
• There is no internet connection.

As you can see, although they’re slightly different, all of these errors indicate a DNS or network misconfiguration. Therefore, they share many of the same solutions, as we’ll see shortly.

Common Causes of DNS_PROBE_FINISHED_BAD_CONFIG

While there are a handful of reasons you might be seeing this message, the good news is that you can at least narrow it down to a DNS or network issue. Some of the most common causes of DNS_PROBE_FINISHED_BAD_CONFIG include:

• Network settings that were accidentally changed
• Router settings changed through an unauthorized app
• Browser plugin(s), such as a VPN app, interfering or messing with the IP or DNS address
• Problematic firewall or antivirus software
• Corrupted files on your device

It’s also possible that the underlying issue is much simpler. For example, the error message may stem from a malfunctioning internet cable or a website that’s temporarily down.

How to Fix the DNS_PROBE_FINISHED_BAD_CONFIG Error Code (7 Ways)

Now that you have a better idea of what this error means, it’s time to get to work.

Before attempting any of the following solutions, we recommend first making sure your internet cables, modem, and router are properly connected. It’s also smart to refresh the web page, just to make sure there wasn’t a temporary glitch with the connection.

Once you eliminate those options, you’re ready to dive in. Let’s take a look at seven potential solutions you can use to fix the DNS_PROBE_FINISHED_BAD_CONFIG error.

1. Restart Your Router

Even if your router is securely hooked up, it may need a quick reboot to reset the IP address. Therefore, the first step is to restart your router.

To do so, simply hold down the power. After leaving it off for at least one minute, power it back on. While it’s restarting, you may also want to restart your computer.

Once both devices are back on, connect to your Wi-Fi or LAN network and try accessing the website again. If you’re still seeing DNS_PROBE_FINISHED_BAD_CONFIG, it’s time to move on to the next method.

2. Clear Your Browser Cache

While this likely isn’t what’s causing the DNS error, it doesn’t hurt to eliminate it as an option. You might want to first try accessing the website from a different browser than the one you’re currently using.

If you can do so successfully, the next logical solution is to clear the cache of the problematic browser.

The process for doing so will look slightly different, depending on your OS and browser. For detailed guidance, you can refer to our post on how to clear your browser cache.

3. Flush the DNS Cache and Renew Your IP Address

If there was a change recently made to your DNS, whether maliciously or accidentally, your system could be trying to use the local cache to connect to the network.

When this is the case, it makes sense that you might receive the DNS_PROBE_FINISHED_BAD_CONFIG message.

Therefore, the next solution to try is flushing your DNS cache, as well as releasing and renewing your IP address. If you’re using Windows 7 or Windows 10, you can do this through the Command Prompt app.

To open Command Prompt, click on the Windows icon/Start button and type “cmd” into the search field. Under Command Prompt, select Run as administrator:

In the Command Prompt window, type in the following commands, hitting the Enter key after each:

ipconfig /flushdns

ipconfig /release

ipconfig /renew

On macOS, you can do this through the Terminal command-line interface. To locate it, click on the Apple icon, followed by Applications > Utilities > Terminal:

In the Terminal interface, the specific command you’ll use varies depending on your macOS version:

• sudo killall -HUP mDNSResponder

  (macOS v10.11 or later)

• sudo discoveryutil mdnsflushcache

  (Yosemite v10.10 through v10.10.3)

• sudo killall -HUP mDNSResponder

  (Mavericks, Mountain Lion and Lion)

• sudo dscacheutil -flushcache

  (Snow Leopard)

To release and renew the IP address, navigate to the Apple menu icon > System Preferences > Network > Advanced > Renew DHCP:

If you’re using an Android device, you can clear your DNS cache by going to Settings > Applications > App info:

From the list of apps, select Chrome (or whatever browser app you’re using), followed by Storage. On the Storage page, click on the Clear Cache button:

Ubuntu users can launch the command Terminal by pressing CTRL + ALT + T, and then input the following command:

sudo systemd-resolve --flush-caches

For more detailed guidance, refer to our guide on how to clear your DNS cache.

4. Manually Change the DNS Settings

If you’re still seeing the DNS_PROBE_FINISHED_BAD_CONFIG error message in your browser, the next thing you can try is changing your DNS settings. Your ISP assigns DNS servers by default.

However, you can temporarily switch to a public DNS server such as Google.

To do this in Windows, right-click on the network icon in the bottom right-hand corner of your screen, then select Open Network and Sharing Center.

Once the Network window opens, right-click on your network connection and select Properties from the drop-down menu:

In the panel that opens, under the Networking tab, select “Internet Protocol Version 4 (TCP/IPv4)” followed by the Properties button:

Under “Use the following DNS server addresses”, enter the following:

• Preferred DNS Server: 8.8.8.8
• Alternate DNS Server: 8.8.4.4

When you’re done, click OK. Refresh your browser and try accessing the website again.

To change your DNS settings for macOS, click on the Apple menu icon, followed by System Preferences > Network. Select your network connection. You can add the new DNS addresses by clicking on the (+) icon:

Android users can locate this option by navigating to Settings > WiFi. Press and hold the network, then click on Modify network:

Click on Advanced options, then under IP settings, select Static:

Enter the IP addresses into the respective fields, and save your changes.

If you’re running Ubuntu OS, you can change your DNS settings by clicking on the gear icon next to your network. Under IPv4 tab, there will be a text field to enter new DNS server addresses:

After you enter them, separating each with a comma, click on the Apply button.

5. Trash Temporary Files

Most browsers and systems will save temporary files to your device to use later.

However, if one of those files is corrupted, it may be what’s causing the DNS_PROBE_FINISHED_BAD_CONFIG error. Therefore, another solution we recommend is deleting your temporary files.

To do this in Windows, type “%temp%” into the search field along your desktop toolbar, and then hit Enter:

This will bring you to the “temp” directory on your computer, where you can view a list of temporary files:

Select all of them and delete them.

On macOS, you can do this by first clicking on Finder and selecting Home (this may be your username instead). Next, hit cmd + shift + . (the period key). This should make your hidden files visible, so you can delete them.

Alternatively, you can try opening Finder and using the Shift + Cmd + G keys. Then, in the text field of the window that opens, enter “~Library/caches”, followed by Enter. This should show you the relevant folders, which you can then delete.

Ubuntu users can skip this step entirely, since the /tmp folder is automatically emptied every time the system is rebooted.

6. Disable Antivirus Software and Firewalls

One of the common issues with antivirus software, firewalls, and VPNs is that they can sometimes conflict with network settings. More specifically, they can interfere with your DNS servers.

Therefore, if you’ve reached this point and the DNS_PROBE_FINISHED_BAD_CONFIG error persists, your next course of action should be to temporarily disable your antivirus software and firewall applications.

Here’s an example using Windows. Click on the Windows icon, then typing “defender” into the search field. Click on Virus & threat protection:

Navigate to Real-time protection, and toggle the switch to Off:

When you’re finished with that, in the left-hand panel, click on Firewall & network protection > Domain network:

Under Windows Defender Firewall, toggle the switch to disable it. Now try accessing the website again.

Of course, the process for doing this will vary based on what system you’re using, as well as what antivirus and firewall software you have installed. If in doubt, check out the developer documentation for your specific software for more details.

You may also want to disable any WordPress security plugins you’re using, on the off chance that they’re causing an issue while you’re working on your website.

7. Update Your Network Drivers

If you’ve made it to this point on the list, it’s likely because you’re still seeing the DNS_PROBE_FINISHED_BAD_CONFIG error message after trying the above fixes. Fortunately, we have one more solution to try: updating your network drivers.

Outdated or corrupted network drivers can cause a variety of issues, including DNS and network interruptions. Windows Updates typically handle the necessary updates for you. However, you can double-check to see whether you can upgrade to the latest version manually.

To do so, type “device manager” into the search field of your taskbar, then click on the Device Manager control panel:

Click on Network adapters, then right-click on the network driver and select Update driver:

Restart your computer, and then try accessing the website again. You should no longer see the DNS_PROBE_FINISHED_BAD_CONFIG message!

Apple handles system and driver updates as well, so this isn’t something you usually have to worry about on macOS. However, if you want to make sure your system is updated, you can do so by navigating to the Apple menu icon > About this Mac and then clicking on Software Update:

If you’re using Android, you can update your device by going to Settings > About Phone/Tablet/Phone/System > System Updates. The path may look slightly different, depending on the type of device you’re using and your version of Android.

Are you experiencing the DNS_PROBE_FINISHED_BAD_CONFIG error? Well, it means there’s an incorrect DNS configuration preventing access to a web page🚪. Here are 7 ways to fix the issue! ✌️Click to Tweet

Summary

There’s nothing fun about trying to access a website, only to find yourself staring at an error message. While irritating, DNS errors are actually quite common.

Fortunately, they’re also relatively easy to resolve and if you’re dealing with the DNS_PROBE_FINISHED_BAD_CONFIG error, here’s how to fix it:

1. Restart your router.
2. Clear your browser cache.
3. Flush the DNS cache and renew your IP address.
4. Manually change the DNS settings.
5. Trash temporary files.
6. Disable antivirus software and firewalls.
7. Update your network drivers.

A lot of users are facing DNS_PROBE_FINISHED_BAD_CONFIG error on Chrome these days. As the name suggests, the problem is related to DNS and quite similar to DNS_PROBE_FINISHED_NXDOMAIN that prevents you from browsing the Internet as usual. Though the problem can occur on any OS including Windows 7, Windows 8, Vista, XP, and Mac OS; the more and more Windows 10 users are reporting the error these days. Keep reading to get better knowledge about DNS, DNS PROBE FINISHED BAD CONFIG issue, and how to fix it on Windows PC as well as a Mac.

What is DNS?

DNS stands for Domain Name System. It is the service that translates domain names into IP addresses. Each network has its DNS system, and if it is unable to translate a domain name into an IP, it will ask another DNS systems, until it returns correct IP.

If DNS server is unable to return correct IP for the domain name, it will most likely return DNS_PROBE_FINISHED_BAD_CONFIG error code. There are lots of reasons for getting this error, and there are several ways to fix it. This error could occur because of the internet provider (ISP), router, computer, or website, so we recommend doing steps until we fix this problem.

How to Fix on DNS_PROBE_FINISHED_BAD_CONFIG on Android

If you are seeing DNS_PROBE_FINISHED_BAD_CONFIG chrome error on Android, here are the possible fixes. Follow the solutions in the same order as mentioned below.

Solution 1: Restart Router

It is possible that the issue is with your router. When you restart the router, it returns all default configurations. If there is any issue that was not there by default, it could be removed by restarting. This is a common solution for all the devices including Android, Windows 10, or Mac. It doesn’t matter which device you are using, restarting router could fix DNS_PROBE_FINISHED_BAD_CONFIG on Android smartphones as well as PC.

Solution 2: Flush DNS Cache on Android

Next solution I will suggest flushing DNS in order to fix DNS_PROBE_FINISHED_BAD_CONFIG on Android.

You can flush DNS by hard reset. Simply take out the battery of your Android device, wait 30 seconds and put it back. Power on your smartphone and see if the problem still exists.

These days we have many high-end smartphones which comes with non-removable battery. For such smartphones, follow the below steps to flush DNS cache.

Step 1: Go to chrome. Type chrome://net-internals/#DNS in address bar. Tap on “Clear Host Cache”

Step 2: Click the black arrow as shown in the image below. Select “Clear Cache” and “Flush Sockets” from the options. Now restart the Chrome.

After flushing the DNS cache, check if it fixes DNS_PROBE_FINISHED_BAD_CONFIG on Android. If you can still see the error, try out next solution.

Solution 3: Renew IP Address on Android

Renewing IP address on Android can fix the DNS probe finished bad config. However, it is not as easy as Windows PC and Mac. So instead of going in depth technical documentation, I will suggest you install ipconfig app available on Google Play. The app will do the job for you.

How to Fix on DNS_PROBE_FINISHED_BAD_CONFIG on Windows 10

If you are a Windows user, the below solutions can fix the problem for once and all. Try one by one until the error is fixed. Please note that these solutions will work on all the Windows versions including Windows 10, 8, 7, Vista, and XP. However, we are performing the steps using a Windows 10 PC. There could be a slight difference in particular settings name; rest will be same for all the versions.

Tip: If you still using an older version of Windows, download Windows 10 ISO file here.

Before we start with the actual solutions, it is necessary to understand where the problem is. If you succeed to access the website from another device on the same network, the problem is most likely in your computer. If this is the case, go directly to solution two. If you cannot access the site from any device on the same network, proceed with solution one.

Similar error: NET::ERR_CERT_AUTHORITY_INVALID

Solution 1: Restart Router

As mentioned above in the Android solutions, restarting router is a common solutions for all the devices including Windows 10 PC. So, start with this easy solution, and if it didn’t work, we could go with advanced settings to fix the DNS PROBE FINISHED BAD CONFIG on your Windows 10 PC.

Solution 2: Disable Firewall and Anti-virus on Windows 10

It could be possible that you are having issues with Firewall, or an antivirus, so we advise you disable them. It can fix the error in minor cases. If it is still there, turn them back on, and keep on following other solutions. Below are the steps on how to turn off Windows firewall.

1. Press Start and type “Firewall” in the search box.

2. Once the Windows firewall option appears, open it, and click on “Turn Windows Firewall on or off.”

3. After that, click on both “Turn off Windows Firewall” for both private and public networks. Then click “OK,” and Firewall is disabled.

Pro Tip: Do you know you can start using Windows 10 Multiple Desktops in a few seconds?

Solution 3: Clean DNS with Command Prompt (CMD)

If the error did not fix in above solutions, try cleaning DNS using Command Prompt. In most of the cases, this solution fixes the DNS_PROBE_FINISHED_BAD_CONFIG error in Chrome. Follow the steps below.

1. Press Start and type “cmd.” When Command Prompt appears, click on “Command Prompt (Admin)” on Windows 10 PC. If you are using Windows 7, 8 or others, right-click on “Command Prompt” option and select “Run as administrator.”

2. In the Command Prompt, paste the “ipconfig/release” command and press Enter.

3. Once the above command is completed, now enter “ipconfig/flushdns“. Hit the enter and wait for the command to execute and complete the process.

4. Now in the next step, run “ipconfig/renew” command same as above commands.

These commands will erase your current DNS and “reset” it.

Solution 4: Change DNS Address in Windows 10

If you are still facing DNS_PROBE_FINISHED_BAD_CONFIG error on Windows 10, 8, 7 or XP, try changing DNS address in the Control panel. To do that, follow the below instructions.

Pro tip: Do you know it is possible to use iMessage on Windows?

1. Open Control panel by pressing Start, and writing “Control panel.”

2. Search for “Network and sharing center” in Control Panel and open it. Now click on “Change adapter settings.”

3. On the Adapter settings page, right-click on the adapter which you are using for the Internet connection and select “Properties.” It should usually be named as your Wi-Fi network name or “Local area connection,” but it is not the case on every device.

4. In the properties, you should see a new window opened with adapter settings. Select your “Internet Protocol Version 4 (TCP/IP)” property, and click on “Properties“. Check picture below for any doubts.

5. Now an another window should open, click on “Use the following DNS addresses”. Under “Preferred DNS address” enter “8.8.8.8”, and under “Alternate DNS server” enter 8.8.4.4. Press “OK,” and check on the browser if that fixed your issue.

If it is not fixed, try switching to Preferred DNS server: 205.67.222.222 and Alternate DNS server: 205.67.220.220. If this also didn’t fix the DNS probe finished bad config error, proceed to next solution.

Solution 5: Reset TCP/IP on Windows 10

It is possible to reset TCP/IP automatically and manually. We do not recommend doing it manually, especially if you don’t know what are you doing, so we advise you go to this link, and follow Microsoft’s instructions that will automatically reset it.

Related Fix: ERR_QUIC_PROTOCOL_ERROR

Solution 6: Reinstall Network Drivers on Windows 10

In most of the cases, the above-given solutions fix the DNS probe finished bad config problem. If your case is different and the problem is still persistent, you should try to reinstall network adapter drivers. If you are using outdated and incompatible Network drivers, you can very well face the DNS_PROBE_FINISHED_BAD_CONFIG in your internet browser or Chrome.

Follow the below steps to check if there is an update available for network drivers.

1. Go to Device Manager. You can search “Device Manager” in the search box and open it.

2. Locate “Network adapters” in the listed options, and expand the “Network adapters” listing.

3. Right click on adapters and click on “Update Drivers.” It will take you to a new window. Here select the “Search automatically for updated driver software.” If Windows find the new drivers, you can update them.

The solutions mentioned above should fix the DNS PROBE FINISHED BAD CONFIG for Chrome in Windows PC.

How to Fix DNS_PROBE_FINISHED_BAD_CONFIG on Mac

Similar to Windows PC users, Mac users also see DNS_PROBE_FINISHED_BAD_CONFIG as the problem is primarily related to DNS. Check out the step-by-step guide below to fix the error on MacBook or iMac.

Solution 1: Renew IP address on Mac

To renew IP address on MacBook, please see the steps below.

1. Click on Apple logo in the top left corner, and select System Preferences.

2. Open Network from System preferences window. Now choose the network you are connected to, and click on Advanced button.

3. Select TCP/IP. After that, click on Renew DHCS Lease, and that will renew your IP address.

Solution 2: Flush DNS on Mac

To flush DNS on Mac, go to Terminal. To open the terminal, you can simply search “Terminal” in the search bar. Alternatively, you can find it on the path “Finder/Applications/Utilities/Terminal.”

When you opened your Terminal, you need to enter one of following lines, depending on your version of operating system.
OS X 10.4 (Tiger): “lookupd -flushcache“.
OS X 10.5 (Leopard) and 10.6 (Snow Leopard): “dscacheutil -flushcache“.
OS X 10.7 (Lion) and 10.8 (Mountain Lion): “sudo killall -HUP mDNSResponder“.
OS X 10.9 (Mavericks): “dscacheutil -flushcache; sudo killall -HUP mDNSResponder“.
OS X 10.10.1, 10.10.2, and 10.10.3: “sudo discoveryutil udnsflushcaches“.
OS X 10.10.4+: “sudo dscacheutil -flushcache;sudo killall -HUP mDNSResponder“.
OS X 11 (El Capitan) and OS X 12 (Sierra): “sudo killall -HUP mDNSResponder“.

Solution 3: Change DNS Address on Mac

For changing DNS on Mac, follow the first two steps as mentioned in the Solution 1 above. Now instead of TCP/IP which we selected in the first solution, choose the DNS tab. Click “+” and add the 8.8.8.8 and 8.8.4.4 DNS addresses. After that, click “OK.”

Let us know your experience with our guide. Were you able to fix DNS_PROBE_FINISHED_BAD_CONFIG Chrome error on Windows 10 or Android or Mac? If the error still exists, comment below with details, and we will help you.

Fix: Service Host Local System (Network Restricted) High Usage

Question

Issue: How to Fix DNS_PROBE_FINISHED_BAD_CONFIG Error?

I’ve been having DNS_PROBE_FINISHED_BAD_CONFIG for a few days now. My PC is not the only device on the network, but it’s the only one receiving this error. I’ve installed Safari and Mozilla Firefox web browsers, although I’m used to use Google Chrome, but DNS_PROBE_FINISHED_BAD_CONFIG appears regardless of web browser I use. I’ve searched for the fixes, but nothing has helped. Maybe you can offer some tips to fix DNS_PROBE_FINISHED_BAD_CONFIG error? Thanks in advance.

Solved Answer

DNS_PROBE_FINISHED_BAD_CONFIG error is the common issue appearing on various systems, so Windows 10 is not an exception. The error mainly shows up in the Google Chrome web browser when the connection is giving you problems, so there is a possible way to fix it.^[1] However, the issue may be caused by other reasons.

DNS_PROBE_FINISHED_BAD_CONFIG is an error related to DNS network service. Usually, the error appears when the user browses the Internet and attempts to visit a random website. Some people claim that DNS_PROBE_FINISHED_BAD_CONFIG error touches Google Chrome only, which is not true.

Since the problem is not related to the browser directly, IE, Mozilla Firefox, and Safari can also be affected. This error occurs due to network problems, faulty configure settings, DNS server inaccessibility or firewall.^[2] Therefore, if the DNS server cannot translate the names of outside servers due to corrupted settings or other reasons, DNS_PROBE_FINISHED_BAD_CONFIG error prevents access to many websites.

DNS_PROBE_FINISHED_BAD_CONFIG error appears on Windows and other devices.

Although that sounds complicated, you don’t have to understand all DNS-related peculiarities to fix DNS_PROBE_FINISHED_BAD_CONFIG error. What you have to do is to follow the instructions that we provide below. Most of the users have successfully dealt with this issue by themselves, so don’t wait any longer.
DNS_PROBE_FINISHED_BAD_CONFIG error message typically says:

Google Chrome can’t display the webpage because your computer isn’t connected to the Internet.
Check your Internet connection
Check any cables and reboot any routers, modems or other network devices you may be using.
Allow Chrome to access the network in your firewall or antivirus settings.
If it is already listed as a program allowed to access the network, try removing it from the list and adding it again.
Error Code: DNS_PROBE_FINISHED_BAD_CONFIG

Since there are a few problems regarding the particular DNS_PROBE_FINISHED_BAD_CONFIG error there are a few options for fixing the issue. In order to keep your device error-free, our recommendation would be to install and regularly use a PC optimization tool, such as ReimageMac Washing Machine X9. Scanning the system with such a program first should help determine the initial issue or even malware.^[3]

Also, we have prepared instructions that should help to fix DNS_PROBE_FINISHED_BAD_CONFIG error, please let us know and we are going to figure out what other fixes can help in your case. But try a few methods at once, at least, before complaining or giving up.

Remove DNS_PROBE_FINISHED_BAD_CONFIG error on Windows

1. Hold Windows Key and Press R.
2. Type cmd in the box and hit Enter to open Command Prompt.
3. When the black window opens, type ipconfig /flushdns command in it and hit Enter.
4. After that, hold Windows key and press R one more time.
   

   DNS_PROBE_FINISHED_BAD_CONFIG error can be fixed via the command prompt window.

5. Type type ncpa.cpl and click OK to access Network Connection.
6. Now we have to update DNS settings, so identify your network adapter in the opened list, right-click on it and select Properties.
7. Find and click on the Internet Protocol Version 4 (TCP/IPv4). Once you click on this option, it should become highlighted in grey. Select Properties.
8. In the new window, mark the Use the following DNS server addresses option.
9. After that, type the following:
   Preferred DNS SERVER: 8.8.8.8
   Alternate DNS SERVER 8.8.4.4
10. Click OK and close all remaining windows.

Clear browser cache

• Go to your Chrome or other browsers.
• Locate Settings in your browser and look for an option Browsing data or History.
• You should now be able to clear cookies and cached data.
  

  Clear your cache and browsing data on the Google Chrome, Mozilla Firefox, Internet Explorer.

Eliminate DNS_PROBE_FINISHED_BAD_CONFIG from Mac OS X

1. Go to the Apple menu, select “System Preferences” and click “Network.”
2. Enter the password (if required to authenticate) to proceed with the changes.
   

   DNS_PROBE_FINISHED_BAD_CONFIG error can be fixed even on Mac OS supporting devices.

3. Select the network connection you want to modify:
   -To change Google Public DNS setting on Ethernet, click on “Built-In Ethernet” and select “Advanced”
   -To change wireless network settings, choose “Airport” and, again, opt for the “Advanced” settings
4. If you want to replace listed addresses click +. Or, you can also add new Google IP address to the list. Type: 8.8.8.8 and 8.8.4.4.
5. When you complete these steps, press apply and OK.

Remove DNS_PROBE_FINISHED_BAD_CONFIG from Android

To change DNS settings on Android, follow these instructions:

1. Open “Settings” and go to “Wi-Fi.”
2. Press-hold your selected network and then click “Modify network.”
3. Opt for the advanced options by marking the “Show advanced options” box.
4. Choose “Static” next to the “IP settings.”
5. Type in DNS servers IP addresses to “DNS 1” and “DNS 2” sections.
6. Click “Save” and reconnect to the network to activate the settings.

Repair your Errors automatically

ugetfix.com team is trying to do its best to help users find the best solutions for eliminating their errors. If you don’t want to struggle with manual repair techniques, please use the automatic software. All recommended products have been tested and approved by our professionals. Tools that you can use to fix your error are listed bellow:

When we manage Windows operating systems we can face a series of errors that can affect both programs, applications, hardware or the system itself and if we do not have a clear concept of what aspect this error encompasses, we may face unpleasant situations..

One of these errors is DNS_PROBE_FINISHED_BAD_CONFIG is a network error , something vital in any system, which involves details such as:

• Faults in the DNS (Domain Name System)

• Internet connection failures

This error will prevent us from accessing the Internet and with it to our favorite websites and for this reason through this tutorial TechnoWikis will give a series of practical tips to give a total solution to this error.

1. Release and renew the IP address to fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

As we access websites, the cache of these sites is hosted in the system so that the next time we visit them the process is much faster, but little by little we accumulate more chache memory which In the end it can be harmful to our use.

The reason for this is that, if for any reason the IP address of the desired website changes, we will not be able to access it because we have another IP address stored and therefore DNS-related errors are generated, such as the DNS_PROBE_FINISHED_BAD_CONFIG error..

To solve this error, we will empty the DNS cache and renew the Windows 10 IP address.

Step 1

To perform this task, we will access the command prompt as administrators and there we will execute the following:

 ipconfig / release (release the IP address) ipconfig / flushdns (empty DNS cache) 

Step 2

Once we have done this, we will renew the IP address by executing the following:

 ipconfig / renew 

2. Edit DNS settings to fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

The DNS is responsible for converting the IP address to domain names and vice versa and when we acquire a new Internet service the DNS is provided by the ISP (Internet Service Provider) but in some situations the DNS_PROBE_FINISHED_BAD_CONFIG error occurs when the DNS server presents some type of error either for maintenance or for some service.

Step 1

In this case we must edit the DNS configuration and for this we will go to the following link:

• Control Panel

• Network and Internet

• Center network and sharing

Step 2

There we will click on the option “Change adapter settings” located on the left side and in the new window we will right click on our network adapter and select the option “Properties”:

Step 3

In the open window we go to the «Internet Protocol version 4» line and click on «Properties»:

Step 4

Now, in the new window we will activate the “Use the following DNS server addresses” box and set the following. These are the IP addresses of Google’s public DNS servers, but we can add some others that we want and that are free. Click on Accept and this will use these servers, which are a guarantee of reliability, for the entire DNS process.

• Preferred DNS server: 8.8.8.8

• Alternative DNS server: 8.8.4.4

3. Restart the router to fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

On many occasions when the modem or router has been turned on for long periods of time it is possible that some type of failures due to overheating, services, etc. may be present. For this, just disconnect or turn off for a moment, between 2 to 4 minutes, and then turn it on again and wait for everything to load in the correct way.

4. Reset the IP catalog fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

The Windows IP catalog is the medium where all the IP addressing carried out in the system is registered and a good practice is to reset it to refresh it and create new redirects since an excess of these can result in the mentioned error.

Step 1

To perform this task, we will access the command prompt as administrators and there we will execute the following:

 netsh int ip reset (This option resets the IP address) 

Step 2

Now we will execute the following:

 netsh winsock reset catalog (This option resets the entire catalog) 

5. Disable antivirus to fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

Although the purpose of the antivirus is to offer an extra layer of security to the system, at times it can cause various errors, among which we have DNS_PROBE_FINISHED_BAD_CONFIG.

Step 1

To validate if our antivirus causes this, we go to the Windows Defender Security Center and there we go to the «Anti-virus and threat protection» section:

Step 2

There, click on the «Antivirus and threat protection settings» line and deactivate the «Real-time protection» switch:

Step 3

Once the antivirus has been disabled, we go to the next route. There we must confirm that the “Activate Firewall” cells are active.

• Control Panel

• Security system

• Windows Defender Firewall

• Customize settings

6. Update the network drivers to fix DNS_PROBE_FINISHED_BAD_CONFIG error in Windows 10

As the operating systems launch new editions, better functionalities or characteristics of the controllers are required so that they respond to these expectations as expected.

Step 1

To update the network drivers in Windows 10, we must access the Device Manager using one of the following options:

Device administrator

Step 2

In the window that appears, we will go to the «Network adapters» section and right click on our network adapter and select the «Update driver» option:

Step 3

The following will be displayed:

Step 4

There we have two options. This will search for the latest versions of the drivers and, if found, will proceed to download and install.

• Search for the controller locally and for this we must go to the manufacturer’s website and download the latest version available.

• Search the driver online

With any of these practical alternatives it will be possible to give a total solution to the DNS_PROBE_FINISHED_BAD_CONFIG error..

You open Chrome and navigate to your favorite website. But instead of the webpage, you get This site can’t be reached, with the error code DNS_PROBE_FINISHED_BAD_CONFIG. This error message indicates that there is something wrong with your DNS settings.

It’s possible that only one device in your network gets this error, but when the problem is related to your DNS server then multiple devices can have the same error. DNS errors are quite common and can easily be fixed.

With the steps below you should be able to get back online in a couple of minutes. We are going to start with the most common solution, that will work for most. If it doesn’t work for you, just go to the next step.

The error message dns_probe_finished_bad_config indicates that your browser is unable to resolve the DNS address. When you visit a website, the domain name will be translated to the corresponding IP address of the webserver.

When your browser is unable to contact the DNS server you will first see the error DNS_PROBE_STARTED followed a few seconds later with the message DNS probe finished bad config. To solve this error we are going to flush the local caches and check our network settings.

1. Flush the local DNS Cache and reset Network Configuration

The first step is to flush the local DNS cache. Your computer keeps a local list of all DNS addresses that you have used. Sometimes it gets outdated or corrupt, which can result in the error dns_probe_finished_bad_config.

To clear the cache we can use a simple command that we can run in PowerShell or command prompt:

1. Right-click on start or press Windows key + X
2. Choose Windows PowerShell or Windows Terminal (on Windows 11)
3. Type all the commands below and press enter after each command:
   • ipconfig /flushdns
   • ipconfig /release
   • ipconfig /renew
   • netsh winsock reset
   • netsh int ip reset

Refresh the webpage to see if the problem is resolved.

2. Change your DNS server

The DNS server that your computer uses is assigned by the modem or router of the network that you are connected with. For your home network is this most of the time the DNS server from your internet service provider.

There could be an issue with the DNS server. DNS records change all the time, but some DNS servers are slow with updating their record. So we are going to change the DNS server that your computer is using to the best DNS server that is available.

You can safely do this, your computer will still work on other networks as well. The steps are slightly different in Windows 11, so I have created different steps for Windows 10 and 11.

Steps for Windows 10 (scroll down for the steps in Windows 11)

1. Right-click your startmenu
2. Select Network Connections
3. Click on Change adapter options
4. Double-click on your (wireless) network adapter

1. Click on Properties
2. Double-click on Internet Protocol version 4 (TCP/IPv4)
3. Enable Use the following DNS servers addresses
4. Enter 1.1.1.1 for preferred and 1.0.0.1 for alternate DNS Server

Click Ok to apply the settings and close all the screens.

Steps for Windows 11

1. Right-click the start menu or press Windows key + X
2. Click on network connections
3. Open Ethernet settings

1. Scroll down and Edit the DNS Server Assignment

1. Change the setting to Manual
2. Enable IPv4
3. Enter 1.1.1.1 as preferred DNS and 1.0.0.1 as alternate DNS

Restart your browser and see if you are able to visit the webpage in question.

If this solution worked for you and the issue occurred in your home network, then change the DNS server settings in your router as well. This way other network devices in your house won’t have any issues either.

3. Disable IPv6 to resolve dns_probe_finished_bad_config

Another command cause of DNS issues like dns_probe_finished_bad_config is the use of IPv6. This new network protocol is turned on by default on most computers these days, but not all networks are configured correctly yet.

So your computer might be using the new IPv6 protocol but is this way unable to resolve the DNS server. We can safely turn off IPv6 in Windows using the following steps (again different steps for Windows 10 and 11)

First steps for Windows 10:

1. Right-click on start or press Windows key + X
2. Open Network Connections
3. Click on Change adapter options

Continue below the steps for Windows 11

First steps for Windows 11

1. Open the start menu
2. Search for Network Connections
3. Open View network connections

Continue here for both Windows 10 and 11

1. Double-click on your (wireless) network adapter
2. Click Properties
3. Turn off Internet Protocol version 6 (TCP/IPv6)

Click Ok to close all the screens and restart your computer. Test the website again to see if the error is resolved.

4. Disable Extensions in Chrome

Browser extensions in Chrome can be de cause of DNS-related issues. Some extensions, like ad blockers, for example, interact with the connection to the website. They block or alter requests send by your browser, resulting in errors like dns_probe_finished_bad_config.

We can simply disable these extensions temporarily to see if they are the cause of the issue.

1. Open Chrome and click on Options
2. Expand More tools
3. Select Extensions

Turn off all extensions and reload the webpage in question. If this solved the problem, then turn the extension on one by one and test between every step if the problem returns. This way you can determine which extension caused the issue.

5. Clear the Chrome DNS Cache

Often not the cause of the issue, but worth a try if all the other steps didn’t help. Chrome also has its own DNS cache. Records in this cache can be outdated or wrong as well. So just to be sure we are going to clear the host cache.

1. Open Chrome
2. Enter the following address in the addressbar: chrome://net-internals/#dns
3. Click on Clear host cache

Reload the webpage to check if the issue is resolved.

6. Turn off internet security software

Keeping your computer secure is important, but some internet security software, like Norton Internet Security, can cause problems with your internet connection. It’s worth a try to turn the software off to see if this resolves the issue “dns probe finished bad config” in Google Chrome

7. Scan your computer for Malware

Some malware is capable of changing your DNS settings, preventing you from accessing the internet (or redirecting your internet traffic). If all the steps above didn’t solve the error dns_probe_finished_bad_config then it is a good idea to run an anti-malware scanner.

A good malware scanner is for example Hitmanpro which you can run with the free trial to see if your computer is infected or not.

Wrapping Up

The Google Chrome error “dns probe finished bad config” is related to an issue with your DNS server. With the steps above you should be able to get back online. Other options that you can try are to restart your router/modem or try a different browser.

If you have any questions, just drop a comment below.