DNS Probe Finished Bad Config: Detailed Solution Methods In Different Situations

DNS Probe Finished Bad Config: Detailed Solution Methods In Different Situations

The two most common and annoying bugs in the Chrome browser are DNS probe finished bad config and Error name resolution failed. Both are associated with domain name mapping errors with the network addresses in your computer (typical for Windows7, Windows8, Windows10, Android and Linux).

What to do? Situations due to which both errors can be different; therefore, the search for a problem must be started from physical devices that are in your network to the computer, for example, a router — first, a little theory about how DNS works.

What is DNS probe finished bad config?

What is DNS probe finished bad config?

The DNS_PROBE_FINISHED_BAD_CONFIG error in Google Chrome most often appears when you make an attempt to enter a resource. From the text itself into errors, you could already assume that the problem could somehow be related to the DNS. DNS functionality is to obtain information about the domain through its name

Why this error happen?

Problems begin when this scenario does not occur. By default, your computer is set to use DNS using a router or modem, which uses your provider’s DNS server, unless it has been changed in any way.

It is always recommended to use public DNS servers, as they are the most stable and reliable solution on the Internet. That is what we will consider today in this article.

Also, a problem in the form of DNS_PROBE_FINISHED_BAD_CONFIG in Google Chrome could be caused due to an incorrect entry in the Hosts file, which may restrict or block access to certain or all resources on the network.

So, let’s go now to the methods for solving the DNS_PROBE_FINISHED_BAD_CONFIG error in Google Chrome, the implementation of which does not take you much time.

How to solve the dns probe finished bad config in a different situation?

Situation 1:Router + computer

compiuters connected to routerWe check the problem by resetting the router (router) and connecting other devices to it. If the error is observed on the phone, laptop, etc., then we think what to do with the router – resets to the factory settings, updating the firmware, reconfiguring the connection with the provider.

If the addresses are fully obtained automatically, including the DNS server, then it makes sense to go to the provider’s forum and consult about the addresses that you can manually specify.

ISP’s DNS servers

In this situation, the router sent a request to Google, and he answered. It can be said that the mapping of names and addresses works. If it does not work, then you should experiment with the ISP’s DNS servers, or specify an alternative – 8.8.8.8, which is stable and serves Google.

In this situation, we see that two DNS are involved in address matching: provider and public from Google. That is, the probability of error is markedly reduced.

Note: It highly depends on the network topology. For example, if the provider uses a VPN connection and the VPN server has a domain name, then without specifying the internal provider DNS, the router will not be able to determine the address of the VPN server. 

Some routers allow you to reset and rebuild the DNS cache with special commands (a similar action will occur with a comprehensive update of the firmware). So consulting on the provider’s forum, as well as a call to technical support may be the best solution. 

You can also search the forum of the manufacturer of the router, and there you can also find specialists (so it’s better to buy not Chinese devices of unknown origin, but brands – Zyxel, Trendnet, Asus, etc.).

At this stage, the most valuable thing is to decide whether to address matching with names on the router works or not. If the router pings domains, then it works, you can go to the computer. If it does not ping, then it is pointless to touch the computer.

Situation 2: Router + computer, everything pinged and opened on the router, on the computer DNS probe finished bad config

First of all, we look at how your network card / wireless adapter interacts with the router.

Very many users use on computers completely dynamic receiving of addresses from a router. It works cool and stable on expensive routers and bad on cheap because of the glitches of the latter.

Connection properties in the network adapter

In this configuration, your router acts as a DNS server, suppose 192.168.1.1, and it is also a gateway. Repeating these settings, prescribing manually, does not make much sense. But you can specify two DNS servers – provider and Google:

From this point on, the computer begins to navigate when comparing names with network addresses to its settings, and not to the router’s DNS. In the Windows console, we ping .us and look at the response from the Google host.

If periodic computer problems occur

Actions in the Windows console (Win + R shortcut key -> cmd and right click on cmd – start as administrator).

Clear DNS cache
ipconfig / flushdns

Resetting Winsock

The service running between the application and the network may fail as a result of viruses and incorrect settings). Press the Win key, then type cmd in the search and right-click on the result — run with administrator rights and command:
netsh winsock reset

DNS in Chrome
Look in Chrome in the address mapping table with names:
Open the Chrome browser and enter in the address bar:
chrome: // net-internals / # dns

During normal operation of the DNS and browser on your computer, you will see the hosts and associated domains:

Clicking Clear host cache will reset the Chrome browser’s cache.

Detailed steps to fix the dns probe finished bad config error in google chrome

  1. Press Win + the R.
  2. Type cmd and press Enter.
  3. Type ipconfig / flushdns in the command line and press Enter. This command will clear the DNS cache, which can sometimes cause this error.
  4. As soon as the cache is cleared, call the Run window again.
  5. Type ncpa.cpl and press Enter to open the Network Connections window.
  6. Find your connection, right-click on it and go to “Properties.”
  7. Select the Internet Protocol Version 4 component from the list and select its properties.
  8. Check the box next to the option that will allow you to use other DNS servers.
  9. Now you need to set in the parameters the very public DNS servers we talked about earlier. Set to 8.8.8.8. For Preferred and 8.8.4.4. For Alternate Address.
  10. Then, confirm the changes, and check for the DNS_PROBE_FINISHED_BAD_CONFIG error in Google Chrome.

Cleaning the Hosts File

Cleaning the Hosts File

If setting public addresses did not give positive results, which is quite likely, then let’s try to clean the Hosts file of possibly interfering domains that are written in it. So do the following:

  1. You need to open the Hosts file itself with a simple Notepad directly. This can be done in many ways, but we will use the simplest. Click Win + R to open the Run utility.
  2. Next, type in the blank line notepad% SystemRoot% \ system32 \ drivers \, etc. \ hosts and press Enter.
  3. Now delete all records of the domains that will be below the line 127.0.0.1 localhost.
  4. Then save the changes to the Hosts file.
  5. Try again on any site and check for the error DNS_PROBE_FINISHED_BAD_CONFIG in Google Chrome.

DNS probe finished bad config in Android

Dns probe finished bad config in Android This problem can also occur in the Chrome browser on the Android OS. The steps are the same – first try to specify the DNS server manually.

In Android, the network settings are hidden in the properties of the access point (long press on the access point), a static address and additionally. The screenshot shows the address of the router as the DNS server and the DNS from Google 8.8.4.4 (the same as 8.8.8.8).

 

 

 

Video to fix DNS probe finished bad config