.org domain not picking up change of nameservers

Hi there

I’ve added a .org domain to CloudFlare and have imported the zone file from the current host.

I’ve asked them to update their nameservers to those specified by CloudFlare but my CloudFlare account still shows the domain as “Pending Nameserver Update”.

The nameservers were updated more than 48 hours ago and if I do an nslookup I can see that the nameservers are correctly updated to CloudFlare.

So, I’m not sure why CloudFlare still thinks the domain is using the old nameservers.

Any suggestions would be greatly appreciated!


And if you actually posted the domain somebody could even have a look :wink:


The domain is microgenerationcertification.org

Thanks for responding :+1:

Usual mistake.

You created NS records at your host instead of changing your nameservers at your registrar. You need to do the latter.

Dig is showing the proper cf nameservers. This may be part of the slowness, whois is showing:

Domain Status: clientDeleteProhibited https://icann.org/epp#clientDeleteProhibited
Domain Status: clientTransferProhibited https://icann.org/epp#clientTransferProhibited
Domain Status: clientUpdateProhibited https://icann.org/epp#clientUpdateProhibited

Security trails shows the name servers https://securitytrails.com/domain/microgenerationcertification.org/history/ns and whatsmydns is showing a token error, https://www.whatsmydns.net/#NS/microgenerationcertification.org

All of this points to your registrar as the next step.

dig @a2.org.afilias-nst.info microgenerationcertification.org NS

;microgenerationcertification.org. IN	NS

microgenerationcertification.org. 86400	IN NS	pdns99.ultradns.biz.
microgenerationcertification.org. 86400	IN NS	pdns99.ultradns.com.
microgenerationcertification.org. 86400	IN NS	pdns99.ultradns.net.
microgenerationcertification.org. 86400	IN NS	pdns99.ultradns.org.
dig +trace microgenerationcertification.org
microgenerationcertification.org. 300 IN NS     cass.ns.cloudflare.com.
microgenerationcertification.org. 300 IN NS     thomas.ns.cloudflare.com.

Thats because of the NS records I mentioned an hour ago :wink:

Seriously, it doesnt get more authoritative than the TLD’s nameservers :wink:

Its the usual mistake. The OP needs to fix his nameservers.

1 Like

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