A website owner who sees DNS_PROBE_FINISHED_NXDOMAIN should first rule out a single visitor's cache or network, then check the domain's own DNS records. Test the address in an incognito window and on another network before you change anything in your DNS zone. The message means Chrome's DNS probe finished, but the resolver decided the name does not exist. NXDOMAIN means non-existent domain, or no DNS records found for that name, according to Cloudflare in Cloudflare's NXDOMAIN troubleshooting guide.
Table of Contents
- Is it only one visitor's problem?
- Do your apex and subdomain records exist?
- Are your nameservers and registration correct?
- What to do after you fix DNS?
Is it only one visitor's problem?
Do not edit your zone on the first report. Hostinger traces this visitor-only version to browser cache, local cache, a bad network, a VPN, or a faulty resolver.
Open the address in an incognito window. Then try another network and another device. If the site loads there, clear the affected browser cache and restart the router before touching DNS.
Do your apex and subdomain records exist?
A missing apex or subdomain record produces exactly this signal. For example, example.com can load while www.example.com fails if www has no record. The IETF defines response code 3 as Non-Existent Domain.
For owners using Cloudflare, Cloudflare advises checking the apex plus active subdomains in the dashboard. Look specifically for example.com alongside active names such as www.example.com or blog.example.com. Point each record to the correct origin IP address. A single typo in the address can keep the subdomain unresolvable.
- Confirm example.com exists.
- Confirm www.example.com exists if you use it.
- Confirm blog.example.com exists if you use it.
- Add any missing apex or subdomain record and correct a wrong origin IP address.
Are your nameservers and registration correct?
Next verify delegation at your registrar. Bluehost advises owners to confirm nameservers point to the right DNS provider, and that the provider holds an authoritative zone, as described in Bluehost's NXDOMAIN guide. Changed nameservers without a matching zone leave visitors with NXDOMAIN.
Then confirm the registration itself is active. Check your registrar account for expiry, suspension, status, or a mistyped name. ICANN notes Whois and RDAP data show registrar, nameservers, creation date, and expiration date.
What to do after you fix DNS?
Allow minutes for the fix to take effect. TTL means time to live, the lifetime set for a cached DNS answer. Old answers can stay cached until that lifetime expires.
Google notes new nameservers or registrars can still return old but unexpired cached answers, as explained in Google's Public DNS troubleshooting notes. After registrar or DNS-host changes, flush the main domain first. Google documents flushing for a domain and record type, plus testing with public resolvers such as Google 8.8.8.8 or Cloudflare 1.1.1.1, in Google's cache-flush guide. Retest in a fresh incognito window after the flush.
