I have a domain at Nominalia, I want to point it to Hostinger, I updated the nameserver records over a week and a half ago, it isn’t propagating. Nominalia told me Cloudflare is the DNS provider for that domain, and that I had to contact Cloudflare to check why the propagation is failing.
What steps have you taken to resolve the issue?
I talked to Nominalia support, they pointed me to Cloudflare.
I talked to Hostinger support, they pointed me to Cloudflare.
Now I’m trying to contact Cloudflare support but I can’t as I can’t select this domain as I don’t have it in Cloudflare.
What feature, service or problem is this related to?
So in this case, as shown in DNS Checker - DNS Check Propagation Tool, NS is only propagated in 2 DNS servers out of 30, the rest show that there is no NS for that domain. I assume this means the issue is on the propagation and not yet on dns-parking.com, right? As until the propagation is finished in all DNS servers dns-parking.com doesn’t have access to that domain. Or is dns-parking.com responsible for finishing the propagation? (In this case dns-parking.com is Hostinger, the service I want to point the NS to)
I’m afraid DNS Checker is not a good tool for what you are using it for here. The nameserver have propagated correctly:
dig +trace +nodnssec weekendbreaks.es
; <<>> DiG 9.18.30-0ubuntu0.24.04.1-Ubuntu <<>> +trace +nodnssec weekendbreaks.es
;; global options: +cmd
...
es. 172800 IN NS a.nic.es.
es. 172800 IN NS c.nic.es.
es. 172800 IN NS g.nic.es.
es. 172800 IN NS h.nic.es.
;; Received 289 bytes from 199.7.91.13#53(d.root-servers.net) in 7 ms
weekendbreaks.es. 86400 IN NS ns2.dns-parking.com.
weekendbreaks.es. 86400 IN NS ns1.dns-parking.com.
;; Received 124 bytes from 2001:678:40::53#53(h.nic.es) in 7 ms
;; Received 45 bytes from 2400:cb00:2049:1::a29f:192a#53(ns2.dns-parking.com) in 25 ms
As you can see from the last line, ns2.dns-parking.com didn’t respond for your domain.
Can you check that you entered your domain correctly on Hostinger, and that these are the 2 Hostinger nameservers assigned to you?
Or did Hostinger give you any reason as for why you should contact Cloudflare?
If some of these tools aren’t seeing exactly what they want to see, they’re sometimes showing something else.
The “dns-parking.com” name servers are responding with code 3 (NXDOMAIN).
This happens no matter whether I query for your domain, or for other domains, such as e.g. example.com.
Why Hostinger is responding with code 3 (NXDOMAIN), rather than code 5 (REFUSED) for domain names that they don’t know about, … is another mystery.
→
Since some of the locations from the DNS Checker tool you’re linking to aren’t able to retrieve the NS records from the “dns-parking.com” name servers, due to the code 3 (NXDOMAIN), then it is becoming quite mixed, regarding what the different locations are showing, where the mix will usually be between:
They cannot find anything.
Responding with the name servers from the delegation, exactly as they appear in the parent registry.
The issue seems to be that your domain hasn’t been configured (properly) on Hostinger, e.g. on the “dns-parking.com” name servers, … yet.
Only Hostinger will be able to assist you with that.
I reopened communications with Hostinger, the first time they told me the issue wasn’t on their side, but now they guided me to add a new site, and on that process I was able to add the domain (which I wasn’t able to do before). Now the domain is functional again.