Skip to content

Commit f38632e

Browse files
Add availability h2 to all custom NSs procedure pages
1 parent 98bea5b commit f38632e

File tree

3 files changed

+12
-7
lines changed

3 files changed

+12
-7
lines changed

src/content/docs/dns/nameservers/custom-nameservers/account-custom-nameservers.mdx

Lines changed: 4 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -16,6 +16,10 @@ import { Example, Render, Tabs, TabItem } from "~/components"
1616

1717
<Render file="acns-tcns-intro" params={{ one: "Account", two: "A", three: "account", four: "zones", five: "account " }} />
1818

19+
## Availability
20+
21+
Account custom nameservers are available for customers on Business (after [contacting Cloudflare Support](/support/contacting-cloudflare-support/)) or Enterprise plans. Once configured, account custom nameservers can be used by all zones in the account, regardless of the zone plan. Via API or on the dashboard.
22+
1923
## Configuration conditions
2024

2125
For this configuration to be possible, a few conditions apply:
@@ -26,13 +30,6 @@ For this configuration to be possible, a few conditions apply:
2630

2731
* Choosing a set from `ns_set 1` through `ns_set 5` will influence how Cloudflare assigns nameservers to your new zones if you configure [DNS zone defaults](/dns/nameservers/nameserver-options/#dns-zone-defaults).
2832

29-
:::caution
30-
31-
* Zone custom nameservers are available for zones on Business or Enterprise plans. Via API or on the dashboard.
32-
* Account custom nameservers are available for customers on Business (after [contacting Cloudflare Support](/support/contacting-cloudflare-support/)) or Enterprise plans. Once configured, account custom nameservers can be used by all zones in the account, regardless of the zone plan. Via API or on the dashboard.
33-
34-
:::
35-
3633
## Enable account custom nameservers
3734

3835
### 1. Set up ACNS names and sets

src/content/docs/dns/nameservers/custom-nameservers/tenant-custom-nameservers.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ import { Example, Render } from "~/components"
1818

1919
<Render file="acns-tcns-intro" params={{ one: "Tenant", two: "T", three: "tenant", four: "accounts", five: "tenant " }} />
2020

21+
## Availability
22+
23+
Tenant custom nameservers, if created by the tenant owner, will be available to all zones belonging to any account that is part of the tenant. Via API only.
24+
2125
## Configuration conditions
2226

2327
For this configuration to be possible, a few conditions apply:

src/content/docs/dns/nameservers/custom-nameservers/zone-custom-nameservers.mdx

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,10 @@ With zone custom nameservers (ZCNS), each custom nameserver name must be a subdo
1818

1919
For example, for a zone `domain.test`, the ZCNS can be `ns1.domain.test` and `ns2.domain.test` but they cannot use a different TLD (`ns1.domain.org`) nor a different domain (`ns1.example.com`).
2020

21+
## Availability
22+
23+
Zone custom nameservers are available for zones on Business or Enterprise plans. Via API or on the dashboard.
24+
2125
## Use zone custom nameservers
2226

2327
### Primary (full setup) zones

0 commit comments

Comments
 (0)