Quick answer: NXDOMAIN means DNS answered “this name does not exist”: the record is missing, the domain's name servers are wrong or lapsed, or the domain itself expired. Check registration status and the A record first — then local DNS cache if only one device is affected.
Overview
Unlike a timeout, NXDOMAIN is a definitive negative answer from DNS. Either the authoritative servers truly have no record for the name, or the resolution chain breaks before reaching them (bad NS delegation, expired domain, suspended zone).
Before you start
- Determine the scope: one device, one network, or everyone? Test on mobile data and with an online checker.
Step-by-step guide
- Check whether the domain is even registered and not expired:
whois example.com | grep -iE 'status|expiry'- Check the delegation and the record at a public resolver:
dig +short NS example.com
dig +short A example.com @1.1.1.1No NS answer → delegation/registration problem at the registrar. NS fine but no A → the record is missing in the zone — create it.
- Exact-name check:
blog.example.comNXDOMAIN whileexample.comworks means only the subdomain record is missing. - If public resolvers answer correctly and only your machine fails, flush the local cache:
sudo resolvectl flush-caches # Linux (systemd-resolved)
ipconfig /flushdns # WindowsCommon issues
- Domain expired yesterday: the most common real cause — renew it at the registrar; restoration can take hours.
- NS switched but zone empty: after moving DNS hosting, recreate all records at the new provider.
- Typo in the hostname: NXDOMAIN faithfully reports names that simply were never created.
- Negative caching: after creating the missing record, the “does not exist” answer stays cached briefly.
When to contact support
Registration and zone contents live with your registrar/DNS provider. But if your domain resolves fine yet the Cloud2Y-hosted site still fails, switch to the general troubleshooting checklist or open a ticket.
Frequently asked questions
What does DNS_PROBE_FINISHED_NXDOMAIN mean?
The browser asked DNS for the name and got a definitive "no such domain" answer — the record does not exist, the delegation is broken, or the domain registration lapsed.
Why does the error appear only on my computer?
If public resolvers return the correct IP, your local cache or network resolver holds a stale negative answer. Flush the OS DNS cache or switch to 1.1.1.1/8.8.8.8 to confirm.
Can an expired domain cause NXDOMAIN?
Yes, it is the most common real-world cause: when registration lapses, the registry pulls the NS delegation and every lookup returns NXDOMAIN until you renew the domain.
Related articles
Need a hand? Contact Cloud2Y support →
