Blog

You are currently viewing DNS_PROBE_FINISHED_BAD_CONFIG in Chrome: Causes and Fixes

DNS_PROBE_FINISHED_BAD_CONFIG in Chrome: Causes and Fixes

When Chrome suddenly refuses to load a website and displays DNS_PROBE_FINISHED_BAD_CONFIG, it means your browser cannot translate the domain name into an IP address because of a local configuration problem. Unlike a full network outage, other devices on the same Wi‑Fi may work fine, and you might still be able to reach sites by IP address. The error is specific to your system’s DNS settings, the hosts file, or a misbehaving proxy. Below you’ll find a structured, safe approach to diagnosing and fixing the issue on Windows, macOS, and Linux.

What Is DNS and Why Does This Error Happen?

The Domain Name System (DNS) acts like a phonebook for the internet. When you type example.com, your operating system sends a query to a DNS server, which replies with the corresponding IP address. If that query fails because the server is unreachable, the response is malformed, or the local resolver is misconfigured, Chrome generates the DNS_PROBE_FINISHED_BAD_CONFIG error. Common triggers include:

  • Incorrect DNS server addresses in your network settings (manual or DHCP).
  • A corrupted DNS cache on your machine.
  • Entries in the hosts file that block or misdirect the domain.
  • Proxy or VPN software that intercepts DNS traffic.
  • Third‑party security suites that override system DNS.
  • Recent changes to network adapters, drivers, or firewall rules.

Step‑by‑Step Fixes (Start With the Safest)

Always begin with the least invasive steps. You do not need admin rights for some checks, but flushing DNS and resetting network adapters typically require elevated privileges. Follow the instructions for your operating system.

1. Restart the Browser and the Machine

Before touching any settings, close all Chrome windows and reopen them. If the error persists, restart your computer. A reboot clears temporary network state and often resolves transient glitches without further intervention.

2. Flush the DNS Cache

Your system caches DNS responses to speed up repeated lookups. A corrupt cache can produce the BAD_CONFIG error. Flushing it forces a fresh query to the configured DNS server.

  • Windows: Open Command Prompt as Administrator and run ipconfig /flushdns. You should see “Successfully flushed the DNS Resolver Cache.”
  • macOS: Open Terminal and run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder. Enter your admin password when prompted. No confirmation message is normal.
  • Linux: The command depends on your DNS resolver. For systemd-resolved, use sudo systemd-resolve --flush-caches. For dnsmasq, restart the service with sudo systemctl restart dnsmasq.

3. Check and Reset the Hosts File

The hosts file maps domain names to IP addresses locally, bypassing DNS. A stray entry (for example, from ad‑blocking tools or malware) can cause the error. Open the file in a plain text editor with admin rights:

  • Windows: C:WindowsSystem32driversetchosts
  • macOS / Linux: /etc/hosts

Look for lines that reference the problematic domain. Remove or comment out any suspicious entries (precede the line with #). Save the file and flush DNS again.

4. Verify DNS Server Settings

Your network adapter may be configured to use an invalid or unreachable DNS server. Temporarily switch to a public, reliable DNS provider to isolate the issue.

  • Windows: Go to Control Panel → Network and Sharing Center → Change adapter settings. Right‑click your active connection, select Properties, then double‑click Internet Protocol Version 4 (TCP/IPv4). Choose “Use the following DNS server addresses” and enter 1.1.1.1 (Cloudflare) and 8.8.8.8 (Google). Click OK and test.
  • macOS: Open System Settings → Network, select your active service (e.g., Wi‑Fi), click Details, then the DNS tab. Remove any existing servers and add 1.1.1.1 and 8.8.8.8.
  • Linux (NetworkManager): Edit the connection in Settings → Network → Wired/Wi‑Fi → IPv4, set DNS to “Automatic (DHCP) addresses only” or manually enter 1.1.1.1, 8.8.8.8.

Windows network adapter properties with manual DNS entries

5. Reset the Network Stack (Windows)

If the error persists, a full network reset can clear misconfigured routes, Winsock catalog, and IP settings. Open Command Prompt as Administrator and run these commands in order:

netsh int ip reset
netsh winsock reset
ipconfig /release
ipconfig /renew
ipconfig /flushdns

Restart your computer afterward.

6. Disable Proxy Settings

A proxy server that is no longer available or incorrectly configured can interfere with DNS resolution. In Chrome, go to Settings → System → Open your computer’s proxy settings. Ensure “Automatically detect settings” is enabled and no manual proxy is listed (unless you specifically need one). On Windows, also check Internet Options → Connections → LAN settings and uncheck “Use a proxy server for your LAN.”

7. Temporarily Disable Security Software

Some antivirus suites include network protection features that hijack DNS to block malicious domains. If you have such software, temporarily disable its web protection module and test Chrome. If the error disappears, add an exception for the affected website or reconfigure the security tool. For a detailed comparison of safe antivirus options, see our article on Best Free Antivirus for Windows 10 Developers: Defender, Bitdefender, Kaspersky, Avast.

Diagnostic Tools for the Curious Developer

If you want to understand the root cause rather than just apply fixes, use command‑line tools to inspect DNS resolution:

  • nslookup example.com – Shows which DNS server is being used and the resolved IP. A “server failed” or “non‑existent domain” response points to a DNS‑side problem.
  • dig example.com – More detailed output than nslookup; available on macOS and Linux by default, and on Windows if you install BIND tools or use WSL.
  • ping example.com – If ping resolves the domain but Chrome does not, the issue is likely browser‑specific (e.g., a corrupted Chrome profile or extension).
  • tracert example.com (Windows) or traceroute example.com (macOS/Linux) – Traces the network path; a timeout at the first hop often indicates a local firewall or misconfigured gateway.

When the Error Appears Only in Chrome

If other browsers (Firefox, Edge) load the site without problems, the culprit is likely a Chrome extension, corrupted user profile, or experimental flag. Try opening Chrome in incognito mode (extensions disabled by default). If that works, disable extensions one by one. You can also create a fresh Chrome profile by renaming the Default folder inside %LOCALAPPDATA%GoogleChromeUser Data (Windows) or ~/Library/Application Support/Google/Chrome (macOS).

Linux‑Specific Considerations

On Linux, the DNS configuration can be managed by systemd-resolved, NetworkManager, resolvconf, or a manual /etc/resolv.conf. Check the current DNS servers with resolvectl status (systemd) or nmcli dev show. If you use a VPN or Docker, their virtual network interfaces may override global DNS. Temporarily disconnect from VPNs and stop Docker containers to see if the error clears.

Preventing Future DNS Probe Errors

Once you have resolved the immediate issue, consider adopting these habits to avoid recurrence:

  • Use a reliable DNS provider (Cloudflare, Quad9, or Google Public DNS) at the router level so all devices benefit.
  • Keep your operating system and network drivers up to date.
  • Regularly flush DNS after installing or uninstalling network‑related software.
  • If you run a local DNS server (e.g., Pi‑hole), monitor its logs for query failures and ensure its upstream servers are responsive.

As a final check, test the problematic domain from a different device on the same network. If that device loads the site, the error is strictly local to your machine. If no device can reach it, the issue lies with your router or ISP, and you should contact your internet service provider.