DNS_PROBE_FINISHED_BAD_CONFIG Fix: Causes and Solutions

DNS_PROBE_FINISHED_BAD_CONFIG is a Chrome error that means the browser attempted a DNS lookup and failed — not because the domain doesn't exist, but because the DNS configuration on the device or network is broken or unreachable.

It's distinct from DNS_PROBE_FINISHED_NXDOMAIN (which means the domain genuinely doesn't exist) and ERR_NAME_NOT_RESOLVED (which is a broader DNS failure). Bad config specifically points to misconfigured DNS settings at the device or network level.

Is It Your Site or the User's Device?

This is the first question. If one user reports this error but the site is accessible to everyone else, the problem is on their end. If multiple users report it simultaneously, or if you see it yourself on your own network while other sites work fine, the DNS configuration is the common factor.

Quick check for website owners:

# Can the domain be resolved from a public resolver?
dig yourdomain.com @8.8.8.8 A +short
dig yourdomain.com @1.1.1.1 A +short

If these return a valid IP, your DNS records are fine. The error is user-side.

Fixes for Users Seeing the Error

1. Release and Renew Your IP / Flush DNS Cache

Windows:

ipconfig /release
ipconfig /flushdns
ipconfig /renew

macOS:

sudo dscacheutil -flushcache
sudo killall -HUP mDNSResponder

Linux:

sudo systemd-resolve --flush-caches

2. Switch to a Public DNS Server

Your ISP's DNS server may be misconfigured or unreachable. Switch to a public resolver:

• Google: 8.8.8.8 / 8.8.4.4
• Cloudflare: 1.1.1.1 / 1.0.0.1

Windows: Network Adapter → IPv4 Properties → set preferred DNS manually.

macOS: System Preferences → Network → Advanced → DNS tab → replace existing entries.

3. Reset TCP/IP Stack (Windows)

netsh int ip reset
netsh winsock reset

Restart after running these.

4. Check Your Router DNS Settings

If all devices on the same network see this error, the problem is the router's DNS configuration. Log into your router admin panel and check the DNS settings — they may have been changed or are pointing to an unreachable server.

Fixes for Website Owners

If your DNS records have recently changed — new hosting, domain migration, NS record update — and users are seeing this error, it may be a propagation issue rather than a configuration problem.

# Check what authoritative nameservers are returning
dig yourdomain.com NS +short

# Query your authoritative NS directly
dig yourdomain.com A @ns1.yourprovider.com +short

If your authoritative nameserver returns the correct IP but public resolvers don't, propagation is still in progress. See DNS propagation taking too long? What to check first for a systematic approach.

If your authoritative nameserver returns nothing or an incorrect record, the DNS record itself needs fixing at your registrar or DNS provider.

Monitoring to Catch DNS Issues Before Users Do

DNS_PROBE_FINISHED_BAD_CONFIG complaints reaching your inbox means users encountered the problem before you knew about it. DNS record monitoring alerts you the moment a record changes unexpectedly or stops resolving correctly.

Domain Monitor monitors your DNS records continuously alongside uptime and SSL — so a broken DNS configuration shows up in your dashboard within minutes, not when a customer emails you. Create a free account.

Related Troubleshooting

• ERR_CONNECTION_TIMED_OUT Fix for Website Owners
• Why Your Domain Points to the Wrong Server
• DNS Propagation Taking Too Long? What to Check First
• Why Your Website Loads for You but Not for Visitors