Fix: dns_probe_finished_bad_config

Browsers suddenly can’t open any website and show “This site can’t be reached” with a DNS_PROBE_FINISHED_BAD_CONFIG error after the computer wakes up, the router restarts, or you change networks. This error means the DNS server settings are wrong, so website names can’t be turned into IP addresses.

This usually happens because the DNS settings are set up incorrectly or are damaged. Common causes include custom DNS entries, problems with the router’s software, or interference from VPN programs.

By default, your computer uses DNS settings provided by your router or modem, which typically come from your Internet Service Provider (ISP) unless you or someone else changed them. If you’re having trouble, switching to public DNS servers (like Google DNS) can improve reliability, as they’re known for being dependable and having high uptime. If you’re new to this, just follow these steps:

  1. Press and hold the Windows key, then press R to open the Run dialog box.
  2. Type cmd and click OK.
  3. In the Command Prompt window that opens, type the following command and press Enter:
    ipconfig /flushdns
  4. This will clear (or “flush”) the DNS cache, which helps remove any old or incorrect DNS details that might be causing the problem.
  5. Once done, press and hold the Windows key and press R again.
  6. Type ncpa.cpl and click OK.
  7. This will open your Network Connections window.
  8. Next, let’s update your DNS settings. Find the network adapter you’re using (usually called “Wi-Fi” or “Ethernet”), right-click on it, and choose Properties.
    dns_probe_finished_bad_config
    Network Adapter Properties
  9. In the Properties window, click on Internet Protocol Version 4 (TCP/IPv4) to select it, then click Properties.
    dns_probe_finished_bad_config
    Changing Settings for IPv4
  10. Select the option Use the following DNS server addresses, then enter these addresses:
    • Preferred DNS Server: 8.8.8.8
    • Alternate DNS Server: 8.8.4.4
    dns_probe_finished_bad_config
    Changing DNS to Public Servers
  11. Click OK to save your changes, and then close any remaining windows.
ABOUT THE AUTHOR

Kamil Anwar


Kamil is a certified MCITP, CCNA (W), CCNA (S) and a former British Computer Society Member with over 9 years of experience Configuring, Deploying and Managing Switches, Firewalls and Domain Controllers also an old-school still active on FreeNode.