Skip to content

Commit 6fceb85

Browse files
Replace Account Settings page occurrences
1 parent 8ed04bc commit 6fceb85

File tree

5 files changed

+49
-25
lines changed

5 files changed

+49
-25
lines changed

src/content/docs/dns/additional-options/dns-zone-defaults.mdx

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@ sidebar:
66
label: Zone defaults
77
---
88

9+
import { DashButton } from "~/components";
10+
911
While there are default values for DNS settings that Cloudflare applies to all new zones, Enterprise accounts have the option to configure their own DNS zone defaults according to their preference.
1012

1113
:::caution
@@ -14,8 +16,11 @@ DNS zone defaults are only applied at the moment a new zone is created and will
1416

1517
## Steps
1618

17-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
18-
2. Go to **Manage Account** > **Configurations** > **DNS Settings**. If these options are not displayed on your Cloudflare dashboard, you may need to reach out to your account team to have them added.
19+
1. In the Cloudflare dashboard, go to the account **Settings** page.
20+
21+
<DashButton url="/?to=/:account/configurations" />
22+
23+
2. Go to **DNS Settings**. If these options are not displayed on your Cloudflare dashboard, you may need to reach out to your account team to have them added.
1924
3. For **DNS zone defaults**, select **Configure defaults**.
2025

2126
The values you select for the listed settings will be automatically applied to new zones as you add them to your Cloudflare account.

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

Lines changed: 16 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ description: With account-level custom nameservers, you can use the same custom
1212
provide the nameservers names do not have to exist as zones in Cloudflare.
1313
---
1414

15-
import { Example, Render, Tabs, TabItem } from "~/components";
15+
import { Example, Render, Tabs, TabItem, DashButton } from "~/components";
1616

1717
<Render
1818
file="acns-tcns-intro"
@@ -62,8 +62,11 @@ For this configuration to be possible, a few conditions apply:
6262
<Tabs syncKey="dashPlusAPI">
6363
<TabItem label="Dashboard">
6464

65-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
66-
2. Go to **Manage Account** > **Configurations** > **DNS Settings**.
65+
1. In the Cloudflare dashboard, go to the account **Settings** page.
66+
67+
<DashButton url="/?to=/:account/configurations" />
68+
69+
2. Go to **DNS Settings**.
6770
3. For **Account custom nameservers**, select **Configure custom nameservers**.
6871
4. Insert a fully qualified domain name for **Nameserver name** and choose a **Nameserver set**. Follow the [configuration conditions](#configuration-conditions).
6972

@@ -131,8 +134,11 @@ To make ACNS the default option for all new zones added to your account from now
131134
<Tabs syncKey="dashPlusAPI">
132135
<TabItem label="Dashboard">
133136

134-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
135-
2. Go to **Manage Account** > **Configurations**.
137+
1. In the Cloudflare dashboard, go to the account **Settings** page.
138+
139+
<DashButton url="/?to=/:account/configurations" />
140+
141+
2. Go to **DNS Settings**.
136142
3. For **DNS zone defaults**, select **Configure defaults**.
137143
4. Change the **Nameserver assignment method** to **Account custom nameservers**.
138144

@@ -182,8 +188,11 @@ Following the [configuration conditions](#configuration-conditions), each set mu
182188
<Tabs syncKey="dashPlusAPI">
183189
<TabItem label="Dashboard">
184190

185-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
186-
2. Go to **Manage Account** > **Configurations** > **DNS Settings**.
191+
1. In the Cloudflare dashboard, go to the account **Settings** page.
192+
193+
<DashButton url="/?to=/:account/configurations" />
194+
195+
2. Go to **DNS Settings**.
187196
3. For **Account custom nameservers**, select **Delete** next to the ACNS name.
188197

189198
</TabItem>

src/content/docs/dns/zone-setups/zone-transfers/access-control-lists/create-new-list.mdx

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Create a new Access Control List
99
---
1010

11-
import { TabItem, Tabs } from "~/components";
11+
import { TabItem, Tabs, DashButton } from "~/components";
1212

1313
You need to create an Access Control List (ACL) if Cloudflare is your [secondary DNS provider](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/). The ACL will specify additional NOTIFY IPs that Cloudflare should listen to.
1414

@@ -18,14 +18,16 @@ An ACL is configured at the account level, which means that it will apply to eve
1818

1919
To create a new ACL using the dashboard:
2020

21-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account.
22-
2. Go to **Manage Account** > **Configurations**.
23-
3. Go to **DNS Zone Transfers**.
24-
4. For **ACL**, click **Create**.
25-
5. Enter the following information:
21+
1. In the Cloudflare dashboard, go to the account **Settings** page.
22+
23+
<DashButton url="/?to=/:account/configurations" />
24+
25+
2. Go to **DNS Settings**.
26+
3. Under **DNS Zone Transfers**, for **ACL**, select **Create**.
27+
4. Enter the following information:
2628
- **ACL name**: Provide a descriptive name.
2729
- **IP range**: Enter a range of IPv4 or IPv6 addresses (limited to a maximum of /24 for IPv4 and /64 for IPv6).
28-
6. Click **Create**.
30+
5. Select **Create**.
2931

3032
</TabItem> <TabItem label="API">
3133

src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-primary/setup.mdx

Lines changed: 9 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Set up outgoing zone transfers (Cloudflare as Primary)
99
---
1010

11-
import { Render, TabItem, Tabs, APIRequest } from "~/components";
11+
import { Render, TabItem, Tabs, APIRequest, DashButton } from "~/components";
1212

1313
With [outgoing zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-primary/), you can keep Cloudflare as your primary DNS provider and use one or more secondary providers for increased availability and fault tolerance.
1414

@@ -64,16 +64,18 @@ You only need to create a peer DNS server if you want:
6464

6565
To create a peer using the dashboard:
6666

67-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account.
68-
2. Go to **Manage Account** > **Configurations**.
69-
3. Select **DNS Zone Transfers**.
70-
4. For **Peer DNS servers**, select **Create**.
71-
5. Enter the following information, paying particular attention to:
67+
1. In the Cloudflare dashboard, go to the account **Settings** page.
68+
69+
<DashButton url="/?to=/:account/configurations" />
70+
71+
2. Go to **DNS Settings**.
72+
3. Under **DNS Zone Transfers**, for **Peer DNS servers**, select **Create**.
73+
4. Enter the following information, paying particular attention to:
7274
- **IP**: If configured, specifies where Cloudflare sends NOTIFY requests to.
7375
- **Port**: Specifies the IP Port for the NOTIFY IP.
7476
- **Enable incremental (IXFR) zone transfers**: Does not apply when you are using Cloudflare as your primary DNS provider (Cloudflare zones always accept IXFR requests).
7577
- **Link an existing TSIG**: If desired, link the TSIG you [previously created](#1-create-tsig-optional).
76-
6. Select **Create**.
78+
5. Select **Create**.
7779

7880
</TabItem> <TabItem label="API">
7981

src/content/docs/dns/zone-setups/zone-transfers/index.mdx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Zone transfers - Multi-provider DNS
99
---
1010

11-
import { Render } from "~/components";
11+
import { Render, DashButton } from "~/components";
1212

1313
To increase availability and fault tolerance, you can use one or more DNS provider(s) alongside Cloudflare in case one provider becomes unavailable (known as a [peer DNS server](#peer-dns-server)). Your providers will then transfer DNS records between themselves using authoritative ([AXFR](https://datatracker.ietf.org/doc/html/rfc5936)) or incremental ([IXFR](https://datatracker.ietf.org/doc/html/rfc1995)) zone transfers.
1414

@@ -25,7 +25,13 @@ Peer DNS servers can be used as primary and secondary external DNS servers. The
2525

2626
<Render file="linked-peers-limit" product="dns" />
2727

28-
You can manage peers via the [API](/api/resources/dns/subresources/zone_transfers/subresources/peers/methods/list/) or the dashboard by going to **Manage Account** > **Configurations** > **DNS Zone Transfers**.
28+
You can manage peers via the [API](/api/resources/dns/subresources/zone_transfers/subresources/peers/methods/list/) or the dashboard:
29+
30+
1. In the Cloudflare dashboard, go to the account **Settings** page.
31+
32+
<DashButton url="/?to=/:account/configurations" />
33+
34+
2. Refer to **DNS Settings** > **DNS Zone Transfers**.
2935

3036
Depending on the usage of the peer, the fields are interpreted in a different way:
3137

0 commit comments

Comments
 (0)