[{"data":1,"prerenderedAt":53},["ShallowReactive",2],{"$f2ps5r729ncwjz":3},{"title":4,"seoTitle":5,"description":6,"route":7,"kind":8,"toolKey":9,"intro":10,"indexable":11,"sections":12,"related":49},"Troubleshoot DNS_PROBE_FINISHED_BAD_CONFIG","Troubleshoot DNS_PROBE_FINISHED_BAD_CONFIG | nslookup.online","Separate local browser and network DNS problems from public DNS configuration errors with a cautious, step-by-step troubleshooting process.","\u002Fguides\u002Fdns-probe-finished-bad-config\u002F","guide",null,"A browser error is a starting point for diagnosis, not proof that a domain is broken.",true,[13,19,25,31,37,43],{"id":14,"title":15,"paragraphs":16},"scope","First establish the scope",[17,18],"Note the exact hostname and whether the problem affects one website or many. Try a known site and another device on the same network. Record any recent VPN, proxy, router or network changes.","Do not post internal domains, credentials or configuration secrets into a public lookup. Queries here go to a third-party resolver, which cannot inspect your device’s private resolver cache or corporate DNS view.",{"id":20,"title":21,"paragraphs":22},"public","Compare a public DNS answer",[23,24],"Look up the name and record type with a chosen public resolver. A successful public response while your browser fails suggests that the browser, operating system, network path or configured resolver deserves further investigation; it does not identify a single certain cause.","An internal corporate name may be intentionally unavailable through public DNS. Replacing the corporate resolver could break access rather than fix it. Consult the network administrator before changing managed settings.",{"id":26,"title":27,"paragraphs":28},"local","Check local configuration safely",[29,30],"Inspect whether your network adapter is configured for automatic DNS or a deliberate custom resolver. Check that addresses were not mistyped. On a managed device, follow the organization’s support process instead of disabling security software or changing policies.","Review active VPN or proxy settings and extension behavior using their supported controls. Do not run untrusted repair scripts or blindly reset all networking in response to a browser error.",{"id":32,"title":33,"paragraphs":34},"cache","Retry after a measured refresh",[35,36],"Restart the browser and reconnect the network if safe. If a stale cache is suspected, consult the operating system’s official guidance for clearing its DNS cache. The exact commands and permissions vary.","Changing a public DNS record does not forcibly clear all recursive and local caches. Keep TTLs and timestamps with your observations, and avoid repeatedly toggling settings without a record of what changed.",{"id":38,"title":39,"paragraphs":40},"zone","When the public lookup also fails",[41,42],"NXDOMAIN, SERVFAIL and a network timeout mean different things. Check the authoritative DNS provider’s status and the registrar’s delegation configuration where relevant. A web page cannot repair those services or verify your local network from the outside.","Try the other supported resolver explicitly if you want a second recursive view. Two matching responses are still not a global propagation measurement, and differences do not automatically make either tool incorrect.",{"id":44,"title":45,"paragraphs":46},"support","Make a useful support report",[47,48],"Collect the affected hostname, time, error message, resolver, record type and whether other devices or networks reproduce it. Leave out private TXT verification tokens and personal browsing history unless your support channel specifically needs them.","Restore intentional settings if an experiment did not help. Escalate persistent failures to your network or DNS provider with the observations, rather than disabling protections or accepting unknown configuration files.",[50,51,52],"\u002F","\u002Fns-lookup\u002F","\u002Fguides\u002Fnslookup-command\u002F",1792661399134]