The Nameservers have been updated and I have checked them on a DNS checker but on Cloudflare, it still says to add the Nameservers.
I have tried removing the site and adding it again and it is still hung up. Any other ideas on how to fix this?
What is the name of your site and which Nameservers are you supposed to use?
plant-it-forward.org is the domain
and here are the nameservers:
kiki.ns.cloudflare.com
koa.ns.cloudflare.com
The nameservers for that domain are:
kiki.ns.cloudflare.com
ns2.hostmonster.com
See also Whois plant-it-forward.org
You probably only changed one of them by accident.
1 Like
That is so strange. I was checking them here:
https://dnschecker.org/#NS/plant-it-forward.org
And it was showing both of them propagated, but it looks like there are still some locations that haven’t propagated. I suppose it could just be a delay in propagation. The change was made 2 days ago which is usually enough time for them to propagate.
No. You need to go back to the settings of your registrar and make the changes, as you have changed only one of the nameservers.
Setting NS records and changing nameservers are 2 very different things. You have set NS records on your old nameservers (which is what dnschecker is showing), but you should have changed the nameservers themselves.
Edit: Actually, it seems you added the NS records on Cloudflare, but that is besides the point.
Edit2: Actually, what I said about NS records might not be true at all. Still, you only changed one of the nameservers.
plant-it-forward.org. 3600 IN NS kiki.ns.cloudflare.com.
plant-it-forward.org. 3600 IN NS ns2.hostmonster.com.
Received 616 bytes from 2001:500:b::1#53(c0.org.afilias-nst.info) in 36 ms
plant-it-forward.org. 86400 IN NS ns1.hostmonster.com.
plant-it-forward.org. 86400 IN NS ns2.hostmonster.com.
;; Received 100 bytes from 162.159.25.186#53(ns2.hostmonster.com) in 188 ms
plant-it-forward.org. 86400 IN NS kiki.ns.cloudflare.com.
plant-it-forward.org. 86400 IN NS koa.ns.cloudflare.com.
;; Received 103 bytes from 2803:f800:50::6ca2:c0b4#53(kiki.ns.cloudflare.com) in 16 ms
The Cloudflare nameserver is just the first one and thus queried by dnschecker. It reports that koa and itself are responsible for the domain.
Just like Hostmaster reports that its nameservers are responsible.
I’m not an expert, but I guess those NS records are implied if none are created explicitly?
1 Like
I did update both of the Nameservers where the domain is registered two days ago (see the image below).
That is what I have always done, it is usually just a lot faster than this.
Then I’d try changing them to something else and back to the Cloudflare nameservers again, because clearly the registrar has updated only one of the nameservers.
Edit: Check the result with dig @a0.org.afilias-nst.info plant-it-forward.org +noall +auth +nottlunits if you have dig available.
This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.