When a domain zone already exists on Cloudflare in a different account

While migrating a client to Cloudflare recently with a zone that was not active on Cloudflare, it eventaually became apparent that the domain had previously been setup on Cloudflare, and that Cloudflare DNS servers would respond to queries using the zone data from the previous account.

Obviously Cloudflare has no way of telling which account is valid, so to contine with the first account makes sense.

However there is a way to resolve this situation where a zone exists in more than one account.

If a new account is created and tries to use a domain zone that has already been created on Cloudflare , then the second account should have some method of verification, such as a DNS TXT record, which if it passes, deactivates the domain from the previous account, and activates it on the new account, if it does not pass, then the previous account would stil be active.

This has the advantage of not impacting valid existing accounts (the test will fail unless they have access to DNS), and allowing valid new accounts to complete setup of the zone and test against the zone before going live and changing the NS records for the domain to point at Cloudflare.

1 Like

Do we have solutions to the above-stated problem?

As I understand it, if the domain is already setup on Cloudflare then Cloudflare gives you a different set of nameservers.

For example original account is setup with ace.ns.cloudflare.com and ben.ns.cloudflare.com.

Then when you setup the site on a different Cloudflare account it should detect that the domain is already pointing to some nameservers and instead provide you with different nameservers for example woz.ns.cloudflare.com and zod.ns.cloudflare.com

Then once you update the domains nameservers to these new nameservers it will take precedence and ignore the old account which will then in turn get automatically removed after 7 days.

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