[DNS] Nameserver assignment consistency #26291
Conversation
github-actions
bot
added
November 2025
product:dns
|
This pull request requires reviews from CODEOWNERS as it changes files that match the following patterns:
|
RebeccaTamachiro
changed the title
|
|
||
| The level of consistency you can expect when adding new zones depends on the nameserver type configured. | ||
|
|
||
| For [standard nameservers](/dns/nameservers/#standard-nameservers), since a conflict can be caused by anyone adding the same zone to any other Cloudflare account, the likelihood of your new zone being assigned different nameserver names than your previously existing ones is way higher. |
There was a problem hiding this comment.
We could add a note that this can be prevented by placing a zone hold on your zone, if it's active already: https://developers.cloudflare.com/fundamentals/account/account-security/zone-holds/
|
|
||
| For [standard nameservers](/dns/nameservers/#standard-nameservers), since a conflict can be caused by anyone adding the same zone to any other Cloudflare account, the likelihood of your new zone being assigned different nameserver names than your previously existing ones is way higher. | ||
|
|
||
| For [account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/), [tenant custom nameservers](/dns/nameservers/custom-nameservers/tenant-custom-nameservers/), and [Foundation DNS advanced nameservers](/dns/foundation-dns/advanced-nameservers/#nameservers-hosting-and-assignment), the only conflict would be between a parent and a child zone, which makes consistent assignment across new zones more likely. |
There was a problem hiding this comment.
With Foundation DNS advanced nameservers, I could have the same conflict if someone else signs up the same zone name in their account, BUT since advanced nameservers is an ENT-only feature the likelihood is significantly smaller.
For account custom nameserver, your statement is correct, since I cannot have two zones with the same name twice in the same account, meaning the only conflict indeed could be between parent and child (or deeper relation).
For tenant custom nameserver, however, there could be a conflict between two zones with the same name in two different accounts, if both accounts belong to the same tenants. But again, the likelihood is very small that this would happen.
|
This PR requires additional review attention because it affects the following areas: RedirectsThis PR changes current filenames or deletes current files. Make sure you have redirects set up to cover the following paths:
|
RebeccaTamachiro
requested review from
a team,
dcpena and
kodster28
as code owners
Co-authored-by: Pedro Sousa <[email protected]>
3 participants
Summary
PCX-13571