Pending NS record update

[dmitri_fedorov]

This is one of the most frustrating experiences I had to deal with in the last few month: I updated NS records five days ago, the record propagation shows them everywhere updated, the registrar reports them properly, the Cloudflare reports all systems operational and yet ICANN (https://lookup.icann.org/lookup) still points to the old data, and my domain edge-sites.com is reported as “pending” by Cloudflare.

My ticket has been ignored.

The only available option to me - the “Re-check now” button - results in NOTHING - no email, no explanation what’s missing/required/why it’s still pending.

Yes I’ve seen “we received too many free support tickets”, but why should I care if you cannot handle your business? You have a free tier and support for it, right?

Unfortunately I depend on having this site at Cloudflare, but this lousy service makes me frantically search for an alternative.

[domjh]

Hi @dmitri_fedorov,

@dmitri_fedorov

updated NS records five days ago

This is the problem, you added NS records instead of changing the authoritative nameservers at your domain registrar.

Community Tip - Fixing “Pending Nameserver Update”

Error Try the suggestions in this Community Tip to help you troubleshoot “Pending Nameserver Update”. Background When you sign up directly with Cloudflare, you’re assigned two name servers, they’ll look something like: tim.ns.cloudflare.com shannon.ns.cloudflare.com Once we confirm the name server change, you’ll see a message on the overview tab of your Cloudflare dashboard that indicates the change was successful and Cloudflare is protecting your site. Until that happens, you’ll see a mes…

[dmitri_fedorov]

Thanks for the tip @domjh, it just illustrates my point of frustration: the most important first step in working with this service refers to this https://support.cloudflare.com/hc/en-us/articles/205195708#434Ce5yZ7oM1ijYPg29SBB
and it does not have a link to AWS Route 53, of course I did it how I find suitable.
It sucks.

[domjh]

Unfortunately Cloudflare can’t include every registrar in that list.

These instructions may apply in your case:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html#domain-name-servers-glue-records-adding-changing

If they work, please let us know and we can ask if they can be added to the list of common registrars to help people in the future.

Your nameservers now seem to correctly point to Cloudflare.

[OliverGrant]

@dmitri_fedorov,

There are several thousand domain registrars. Amazon documents their process… no idea if it is accurate as I don’t use them.

https://www.google.com/search?q=how+to+change+your+nameservers+route+53+registrar&rlz=1CDGOYI_enUS768US768&oq=how+to+change+your+nameservers+route+53+registrar&aqs=chrome..69i57.17365j0j4&hl=en-US&sourceid=chrome-mobile&ie=UTF-8

[dmitri_fedorov]

Thank you guys, I did find how to do it on my own after I was pointed out that I need to change the authoritative nameservers, it’s not difficult to do on AWS Route 53 when you know what to change.

All it would take on the Cloudflare “Complete your nameserver setup” page for the site to say authoritative nameservers and then I would do it properly five days ago.

Words matter

[domjh]

No problem, glad you managed to get it sorted. Can I just check that these instructions match your experience with changing them, before passing them on?

I will make sure to pass your feedback on.

[dmitri_fedorov]

Yes, these are correct instructions.

[domjh]

Great, thank you. Please just let us know if you have any further questions!

[dmitri_fedorov]

Thank you, I will.