DNS_PROBE_FINISHED_NXDOMAIN means your browser asked DNS for your domain's IP address and got back "this domain doesn't exist." It's not a server problem, it's a DNS problem: either the domain has expired, the nameservers are wrong, the DNS change hasn't propagated yet, or your own device has a stale cache. Work through these in order.
Check if the domain expired
An expired domain stops resolving entirely, and this error is exactly what you'll see. Sign in to portal.flashcloud.com, go to Domains, and check the expiration date next to the domain in question. If it's past due:
- Renew it from the domain's page in the portal.
- If the domain is in the grace period, renewal usually restores it, but resolution can take a little while to come back once the registry reactivates it.
- If you see a suspended or redemption status instead of a simple "expired" label, open a support ticket. Domains in redemption often need registry-level action, not just a renewal payment.
Check the nameservers
If the domain is active, the next most common cause is nameservers pointed at the wrong place, most often after a domain transfer or a manual DNS provider change. In the portal, go to Domains, click the domain, and check the nameserver settings. For domains hosted with us, they should point to ns1.flashcloud.com and ns2.flashcloud.com.
If the nameservers were recently changed (either to ours or away from ours), that change itself needs to propagate before resolution works. See the next section.
If the nameservers are correct but the domain still won't resolve, check the DNS records themselves under the domain's DNS subpage. A missing or deleted A record for the root domain (or CNAME for a subdomain) will also produce NXDOMAIN, since there's no record to answer with even though the domain itself exists.
Give it time to propagate
Nameserver and DNS record changes don't take effect everywhere instantly. Resolvers around the world cache the old answer until their cache expires. For domains using our nameservers, most changes are visible within a minute or two; changes made elsewhere can take longer. The full mechanics and expected timeframes are in How long does DNS propagation take?, including how to check propagation status with a checker tool instead of guessing.
If you just made a nameserver or DNS change and it's been less than an hour, this is the most likely explanation. Wait it out before troubleshooting further.
Clear your local DNS cache
Sometimes everyone else's DNS has already updated, but your own computer or browser is still holding onto the old (empty) answer. This shows up as NXDOMAIN for you specifically while the site loads fine elsewhere.
- macOS:
sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder - Windows:
ipconfig /flushdns - Linux (systemd-resolved):
sudo resolvectl flush-caches - Chrome: visit
chrome://net-internals/#dnsand click "Clear host cache"
If flushing your local cache doesn't help, try switching your device's DNS resolver to 1.1.1.1 or 8.8.8.8 to rule out your ISP's resolver serving a stale answer.
Rule out a browser-only issue
Test the domain in a different browser or from your phone on cellular data (not the same wifi). If it resolves elsewhere but not in your primary browser, it's a local cache or a browser extension, not an actual DNS problem with the domain.
When to contact support
If the domain isn't expired, the nameservers and DNS records look correct, and it's been more than a few hours with no change, open a ticket from Support > New ticket in the portal, or use live chat. Have the domain name and roughly when the DNS change was made ready. This is especially worth doing quickly if the domain shows a suspended or redemption status, since those need us to act on the registry side.