Skip to content

Commit 548ad11

Browse files
Adjust page structure and revert unnecessary edits
1 parent d80de41 commit 548ad11

File tree

1 file changed

+9
-3
lines changed

1 file changed

+9
-3
lines changed

src/content/docs/dns/nameservers/nameserver-options.mdx

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,17 @@ Refer to the sections below to learn about different nameserver options.
1212

1313
## Assignment method
1414

15-
When you add a domain on a full or secondary setup, Cloudflare automatically assigns your nameservers. The default assignment method is to use standard nameservers and favor consistent nameserver names across all zones within an account. Nonetheless, in case there are conflicts — for example, if someone else has already added the same zone to a different account — you may get different nameserver names. To have control over what nameservers are assigned for different zones within an account, you can use account custom nameservers
15+
When you add a domain on a full or secondary setup, Cloudflare automatically assigns your nameservers.
1616

17-
## Nameserver Assignment Consistency
17+
The [default assignment method](/dns/zone-setups/reference/nameserver-assignment/) is to use standard nameservers and favor consistent nameserver names across all zones within an account. Nonetheless, in case there are conflicts — for example, if someone else has already added the same zone to a different account — you may get different nameserver names.
1818

19-
The level of consistency you can expect when adding new zones depends on the nameserver type configured. For Standard nameservers, assignment is a best-effort approach, and there is no guarantee that all new zones will receive the same set if a conflict is detected. For Account Custom Nameservers (and Tenant Custom Nameservers) and Foundation DNS advanced nameservers, the likelihood of consistent assignment across new zones is significantly higher. The only common reason for an inconsistent set is an internal conflict, such as a parent and child zone ($example.com$ and $[www.example.com](https://www.example.com)$) needing different nameserver sets to prevent delegation issues.
19+
To have control over what nameservers are assigned for different zones within an account, you can use [account custom nameservers](/dns/nameservers/custom-nameservers/account-custom-nameservers/).
20+
21+
### Nameserver consistency
22+
23+
The level of consistency you can expect when adding new zones depends on the nameserver type configured. For standard nameservers, assignment is a best-effort approach, and there is no guarantee that all new zones will receive the same set if a conflict is detected.
24+
25+
For Account Custom Nameservers (and Tenant Custom Nameservers) and Foundation DNS advanced nameservers, the likelihood of consistent assignment across new zones is significantly higher. The only common reason for an inconsistent set is an internal conflict, such as a parent and child zone ($example.com$ and $[www.example.com](https://www.example.com)$) needing different nameserver sets to prevent delegation issues.
2026

2127
### DNS zone defaults
2228

0 commit comments

Comments
 (0)