CF not activating Domain. NS pointing to CF since days already

[markus10]

What is the name of the domain?

pulch.net

What is the error message?

This zone isn’t activated yet. Please make sure to point your domain to Cloudflare’s nameservers before using Email Routing.

What is the issue you’re encountering

Zone does not get activated

What steps have you taken to resolve the issue?

Review docs, monitor public resolution of this domain on various nameservers

What feature, service or problem is this related to?

Nameservers

What are the steps to reproduce the issue?

point NS records to CF on origin DNS provider (AWS) and wait some days.

[sjr]

@markus10

point NS records to CF on origin DNS provider (AWS) and wait some days.

That’s not the correct thing to do. You need to change the authoritative nameservers for your domain from AWS to Cloudflare, not add NS records to the DNS…
https://cf.sjr.dev/tools/check?22280af59c3e421fb7b010b9669dc088#rdap

[markus10]

I followed the instructions on CF docs and added mira.ns.cloudflare.com and mitch.ns.cloudflare.com as NS entries on AWS side. Also I removed the AWS specific entries.
Those are now reflected since days on majority of public DNS servers: DNS Propagation Checker - Global DNS Testing Tool

What did I miss ?

Thanks, Markus

[sjr]

@markus10

added mira.ns.cloudflare.com and mitch.ns.cloudflare.com as NS entries on AWS side

As above, that’s not the right thing to do. You need to change the authoratitve nameservers. Here’s the AWS guide that Cloudflare links to that tells you what to do…

Adding or changing name servers and glue records for a domain - Amazon Route 53

[markus10]

As is says either change DNS OR auth DNS servers I changed the NS server entries in AWS side.

[markus10]

Also here:

I added as requested the two new entries and removed the AWS related ones:

[markus10]

I added as requested the two new entries and removed the AWS related ones:

[markus10]

Taking a look at this message it seems to be more a caching issue?

If it’s not a caching issue, which step of the doc am I missing?
Sorry slitting it into multiple messages, but more than 1 attachment/message is not allowed.

regards, Markus

[sjr]

@markus10

As is says either change DNS OR auth DNS servers I changed the NS server entries in AWS side.

Setting NS records for the domain in the zone for the domain has no effect so does not change the nameservers. You need to do what I said and follow the instructions in the AWS link I posted above. It will not work any other way.

@markus10

Taking a look at this message it seems to be more a caching issue?

The message says “You may have added NS records to the DNS instead of setting them at your registrar” - which is exactly what you have done.

[markus10]

Problem fixed…

for the protocol if someone has the same issue:
Do not change the hosted zone, change the setting on the domain itself