Back to Troubleshooting Browse tutorials on the blog

DNS Errors

What the error means and common fixes.

DNS errors like DNS_PROBE_FINISHED_BAD_CONFIG usually mean your device cannot translate a domain name into the correct IP address. In most cases, that points to a local DNS problem on your browser, device, router, or internet provider rather than a problem with the website itself.

What this error usually means

  • Your DNS resolver returned a bad answer: the network may be using slow, outdated, or broken DNS servers.
  • Your device cached an incorrect record: browsers, operating systems, and routers can temporarily hold onto bad DNS results.
  • Your network changed recently: switching WiFi networks, VPNs, firewall tools, or custom DNS settings can cause conflicts.
  • Your ISP DNS is having issues: the site may work for other people while failing only on your connection.

Quick fixes to try first

  • Refresh the page and restart your browser.
  • Restart your device.
  • Power cycle your router or modem if you control the network.
  • Try a different network, such as mobile data instead of WiFi.
  • Temporarily disable a VPN, DNS filter, or security app that changes network settings.

Switch to Cloudflare DNS

Using a public DNS provider can often fix DNS resolution problems quickly. Cloudflare DNS is a common option that many users switch to when their default DNS is unreliable.

  • Primary IPv4 DNS: 1.1.1.1
  • Secondary IPv4 DNS: 1.0.0.1

To change DNS on most devices:

  1. Open your device's network or internet settings.
  2. Select your active connection, such as WiFi or Ethernet.
  3. Find the DNS settings section. It may be under Advanced, Manual DNS, or Configure DNS.
  4. Replace the current DNS servers with 1.1.1.1 and 1.0.0.1.
  5. Save the change, disconnect and reconnect to the network, then reopen your browser.

After changing DNS

  • Wait a minute, then load the page again.
  • If the error continues, turn airplane mode on and off or restart the device once more.
  • If you are on a work, school, or managed network, DNS settings may be locked by an administrator.

If the issue still is not fixed

The next step is usually clearing local DNS cache or checking whether the domain itself is returning an NXDOMAIN response. For a deeper walkthrough, see our DNS troubleshooting guide.

Need more help?

If you still have questions, contact [email protected] or use the contact form. For abuse or suspicious links, use Report Abuse. For feature requests, email [email protected].

Contact Support API Docs Blog