aprilmintacpineda.com
The domain is still in Pending NS Update state even after changing the domain’s NS to cloudflare.
DNS not responding/updating
You have just adjusted some NS records within your current DNS provider.
You need to get the delegation of name servers changed in the parent registry, through your domain registrar.
ns-1282.awsdns-32.org
ns-1886.awsdns-43.co.uk
ns-415.awsdns-51.com
ns-742.awsdns-28.net
is still the name servers in the parent registry for that domain.
Is there anyway I could force the parent registry to update the NS?
The correct way to do this is to update the WHOIS info at your domain registrar.
What do you mean? Can you give me a more detailed answer or point me to a link somewhere that explains it? I don’t want to transfer my domain from AWS Route53 to Cloudflare.
My hunch is it might be that the NS haven’t fully updated yet because the last record has 2 days TTL.
Did you see these directions for Amazon? You can find a link in the expandable section labeled Provider-specific instructions.
I have already updated the records
in a lot of places it’s already pointing to cloudflare DNS Propagation Checker - Global DNS Testing Tool there are only 2 places that haven’t updated for some reason.
If you did it right, your SOA record would point to Cloudflare. Give that a look at DNSChecker (or whatever tool you’re using).
Hmmm… some are pointing to CF some are not.
I’ve done this before when I pointed GoDaddy domain to Route53, also namecheap to Route53 and vice-versa, it didn’t take this long.
Two different implementations may be behaving, … well, differently.
It can therefore be a good idea, to check multiple sites for what they have to say about the domain.
The result is the same as previously, the delegation of name servers for the mentioned domain name has NOT been changed to Cloudflare, … yet.
If @epic.network’s reference above wasn’t enough, try this:
→ Adding or changing name servers and glue records for a domain - Amazon Route 53
That isn’t the case, as the name server delegation still hasn’t been changed.
Nothing will ever happen, or change, when the delegation hasn’t been changed (properly).
Checking with domain WHOIS, “dig +trace” and various domain health checkers will confirm the above, that the change hasn’t been done (properly).
It will take in the area of 48 - 96 hours, starting from the point when the delegation has been changed successfully.
