It’s been days since I changed the nameservers and Cloudflare still hasn’t processed them. I requested analysis a few days ago too, and it still hasn’t processed my site. I checked on who.is and other sites, and the nameservers are already updated correctly.
What steps have you taken to resolve the issue?
I analyzed possible problems end-to-end, and I couldn’t find any cause other than Cloudflare’s system. There’s not much you can do when the site isn’t processed by other systems bigger. I think it’s just an internal error in my site’s DNS processing.
What feature, service or problem is this related to?
You should contact your domain registrar and ask them to remove DNSSEC then the propagation should complete and you’ll be good to go. Let us know how it works out.
It was working. At least, Hostinger (the registrar I use) displayed its own website when I tried to access my site, indicating that there was no content to be hosted and I only had the domain. After I changed the nameservers, the page became inaccessible, giving an error like “URL not found”. My idea was to buy the domain, associate it with Cloudflare and use Cloudflare Tunnel.
As the old adage goes, correlation does not imply causation.
Your domain has serverHold on it, as you’ve been told already. From Hostinger themselves, this means the domain is suspended.
Since it was recently registered, the likely cause is that you did not act on some verification email Hostinger sent you upon registering the domain.
This is not caused by changing nameservers: it’s a mere coincidence.
If you’re not convinced, just change the nameservers back to whatever it was and let’s see if the domain works now.
But your time will be better spent working with Hostinger (your registrar) to have the serverHold lifted, rather than doubling down on the incorrect attribution.
It’s not about not being convinced; I retired from IT a few years ago, and now I only get involved when necessary. I don’t know much and I stopped studying.
Before formally contacting the registrar for a request, I thought it was valid to have this suspicion serverHold as the possible main cause for the problem — coming from someone who is, yes, in the know.
I will follow up with the registrar. I’ll come back if this doesn’t solve the problem.