The site got down suddenly with "DNS_PROBE_FINISHED_NXDOMAIN" and "ERR_NAME_NOT_RESOLVED" error

I did not change any settings but my site have got to be unreachable suddenly with the error message “DNS_PROBE_FINISHED_NXDOMAIN” (on my laptop).

Also as a strange thing it also showed “ERR_NAME_NOT_RESOLVED” when I tried accessing with my smartphone, using the same Wi-Fi.

The web server seemes to be working well.
I cleared the cache on the browser and purged cache on cloudflare but the site wouldn’t come back for this 6 hours.

What else should I do for this?

What is the domain name?

sayosan.cf

https://dnsviz.net/d/sayosan.cf/dnssec/

Freenom .cf/.tk domains…

https://www.reddit.com/r/freenom/comments/1akf1cv/every_domain_is_now_down/

Your domain now does not resolve from the registry…

dig +trace +nodnssec -4 sayosan.cf

; <<>> DiG 9.18.18-0ubuntu0.22.04.1-Ubuntu <<>> +trace +nodnssec -4 sayosan.cf
;; global options: +cmd
.			5252	IN	NS	c.root-servers.net.
.			5252	IN	NS	l.root-servers.net.
.			5252	IN	NS	k.root-servers.net.
.			5252	IN	NS	h.root-servers.net.
.			5252	IN	NS	b.root-servers.net.
.			5252	IN	NS	d.root-servers.net.
.			5252	IN	NS	i.root-servers.net.
.			5252	IN	NS	g.root-servers.net.
.			5252	IN	NS	f.root-servers.net.
.			5252	IN	NS	a.root-servers.net.
.			5252	IN	NS	m.root-servers.net.
.			5252	IN	NS	j.root-servers.net.
.			5252	IN	NS	e.root-servers.net.
;; Received 239 bytes from 127.0.0.53#53(127.0.0.53) in 0 ms

cf.			172800	IN	NS	a.ns.cf.
cf.			172800	IN	NS	b.ns.cf.
cf.			172800	IN	NS	c.ns.cf.
cf.			172800	IN	NS	d.ns.cf.
;; Received 282 bytes from 198.41.0.4#53(a.root-servers.net) in 4 ms

cf.			5	IN	SOA	a.ns.cf. kohilaire.socatel.cf. 1707402870 10800 3600 604800 5
;; Received 130 bytes from 185.21.168.17#53(a.ns.cf) in 120 ms

thank you so much. As of my understanding from the link it is a problem caused by freenom and the .cf domains issue, so there is nothing that i can do for this…?

2 Likes

There’s nothing you can do. I would suggest you buy a regular domain with a more reputable registrar (Cloudflare sells domains at cost). Even if, as some in that thread have said, the domain comes back it’s clear that it can’t be relied on to stay active.

2 Likes

understood. I should probably replace it to more rigid domains if it’s not going to come back. I confirmed the risk for choosing a niche domains. Again thank you very much for giving the solution this quick.

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.