Usually, Cloudflare would give you 2 nameserver like:
maria.ns.cloudflare.com
tony.ns.cloudflare.com
It’s random.
You change the nameserver at the registar to Cloudflare ones, the resolve is handled by Cloudflare after propagation.
You would notice that all domains added in your Cloudflare account use the same 2 nameserver, unless you are already using Cloudflare’s namever before adding domain to Cloudflare
Then Cloudflare would give you 2 different nameserver, which is quite annoying.
Why?
Because you already know the nameserver, but you can’t pre-fill it.
Let’s assume a scenario:
Your customer forgets to renew the domain.
Cloudflare deletes the domain after 7 days.
Then the customer renews the domain.
The domain name service provider will automatically restore the nameserver from expiration to the nameserver previously set by the user to make the domain name available again.
But if customer re-add domain in Cloudflare, Cloudflare would give him two new one, which makes the automatical recovery useless.
Sometimes you can get the old Zone records back, sometimes you need to re-add DKIM and a bunch of verification records.
Clouflare has made some improvements, such as no longer forcing the scanning of records when adding websites, but providing three options: scanning, manual adding, and importing, and the ability to delete records in batches.
But I think there is still room for improvement in processes and strategies, such as using Websites Push to transfer domains between accounts or using EPP to verify ownership, and sending the exported Zone file to users before deleting the domain, or providing an option of “The domain is renewed or redeemed, recover it”.
