Skip to content

Commit 3fe14e2

Browse files
[DNS] Use DashButton zone level (#25982)
* Windsurf first pass to manage-dns-records folder * Manual edits to edge cases * Second pass, avoiding OL formatting if single line * Third batch, excluding zone-conversion files that needed edits * Replace other instances of previous navigation notation * Manual edits for remaining files * Fix wrong path in convert-partial-to-secondary * Inspect and apply changes to dns partials
1 parent a1f328e commit 3fe14e2

36 files changed

+221
-155
lines changed

src/content/docs/dns/additional-options/analytics.mdx

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66

77
---
88

9-
import { FeatureTable, Details } from "~/components"
9+
import { FeatureTable, Details, DashButton } from "~/components"
1010

1111
When you use Cloudflare DNS, you can access data about DNS queries through a variety of sources.
1212

@@ -28,8 +28,7 @@ When using GraphQL, you also have the option to get data for DNS queries across
2828

2929
For a quick summary, view your DNS analytics on the dashboard:
3030

31-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
32-
2. Go to **DNS** > **Analytics**.
31+
<DashButton url="/?to=/:account/:zone/dns/analytics" />
3332

3433
The DNS analytics dashboard contains [four main panels](#dns-analytics-panels). The filters and time frame that you specify at the top of the page apply to all of them.
3534

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
1111
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.
1212

1313
:::caution
14-
DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted within each zone, on the respective [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) or [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page.
14+
DNS zone defaults are only applied at the moment a new zone is created and will not impact already existing zones. Any of the values specified as default can later be adjusted within each zone, on the respective [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) or [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page.
1515
:::
1616

1717
## Steps

src/content/docs/dns/additional-options/reverse-zones.mdx

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 5
66
---
77

8-
import { Details, Example } from "~/components"
8+
import { Details, Example, DashButton } from "~/components"
99

1010
If you control your own IP prefix(es), you can set up reverse zones with PTR records to allow reverse DNS lookups.
1111

@@ -71,7 +71,9 @@ To set up a reverse zone, you need to create a reverse DNS zone and add PTR reco
7171

7272
### 2. Add PTR records
7373

74-
1. Go to **DNS** > **Records**.
74+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
75+
76+
<DashButton url="/?to=/:account/:zone/dns/records" />
7577

7678
2. For each IP within the prefix, add a PTR record using the least significant octet(s) as the subdomain.
7779

src/content/docs/dns/cname-flattening/set-up-cname-flattening.mdx

Lines changed: 10 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Set up CNAME flattening
99
---
1010

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

1313
:::note
1414

@@ -26,9 +26,11 @@ For zones on paid plans, you can choose to flatten all CNAME records. This optio
2626

2727
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
2828

29-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
30-
2. Go to **DNS** > **Settings**.
31-
3. Turn on the option **CNAME flattening for all CNAME records**.
29+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
30+
31+
<DashButton url="/?to=/:account/:zone/dns/settings" />
32+
33+
2. Turn on the option **CNAME flattening for all CNAME records**.
3234

3335
</TabItem> <TabItem label="API">
3436

@@ -49,11 +51,10 @@ If you use this option, a special [tag](/dns/manage-dns-records/reference/record
4951

5052
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
5153

52-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
53-
2. In **DNS** > **Settings**, make sure that **CNAME flattening for all CNAME records** is turned off.
54-
3. Go to **DNS** > **Records** and find the CNAME record you would like to flatten.
55-
4. Select **Edit** and turn on the **Flatten** option.
56-
5. Select **Save** to confirm.
54+
1. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, make sure that **CNAME flattening for all CNAME records** is turned off.
55+
2. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and find the CNAME record you would like to flatten.
56+
3. Select **Edit** and turn on the **Flatten** option.
57+
4. Select **Save** to confirm.
5758

5859
:::note[Unavailable flatten option]
5960
For the following cases, **Flatten** will not be available:

src/content/docs/dns/dnssec/dnssec-active-migration.mdx

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -36,7 +36,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the
3636

3737
To import the zone file using the API, refer to the [Import DNS Records endpoint](/api/resources/dns/subresources/records/methods/import/).
3838

39-
3. Go to **DNS** > **Settings**, and select **Enable DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
39+
3. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, select **Enable DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
4040

4141
<APIRequest
4242
path="/zones/{zone_id}/dnssec"
@@ -46,7 +46,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the
4646
}}
4747
/>
4848

49-
4. Go to **DNS** > **Settings**, and enable **Multi-signer DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
49+
4. On the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, enable **Multi-signer DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
5050

5151
<APIRequest
5252
path="/zones/{zone_id}/dnssec"
@@ -135,8 +135,8 @@ multisigner.info. 3600 IN DNSKEY 256 3 13 pxEU<bla_bla_bla>0xOg==
135135

136136
## 3. Set up registrar
137137

138-
1. Add Cloudflare DS record to your registrar. You can see your Cloudflare DS record on the [dashboard](https://dash.cloudflare.com/?to=/:account/:zone/dns) by going to **DNS** > **Settings** > **DS Record**.
139-
2. Add Cloudflare assigned nameservers to your registrar. You can see your Cloudflare nameservers by going to **DNS** > **Records**.
138+
1. Add Cloudflare DS record to your registrar. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
139+
2. Add Cloudflare assigned nameservers to your registrar. You can see your Cloudflare nameservers on the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page
140140

141141
At this point your zone is in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/).
142142

src/content/docs/dns/dnssec/multi-signer-dnssec/setup.mdx

Lines changed: 18 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66
label: Setup
77
---
88

9-
import { Tabs, TabItem, APIRequest } from "~/components";
9+
import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
1010

1111
This page explains how you can enable [multi-signer DNSSEC](/dns/dnssec/multi-signer-dnssec/about/) with Cloudflare, using the [model 2](/dns/dnssec/multi-signer-dnssec/about/#model-2) as described in [RFC 8901](https://www.rfc-editor.org/rfc/rfc8901.html).
1212

@@ -16,7 +16,7 @@ Note that:
1616

1717
- This process requires that your other DNS provider(s) also support multi-signer DNSSEC.
1818
- Although you can complete a few steps via the dashboard, currently the whole process can only be completed using the API.
19-
- Enabling **DNSSEC** and **Multi-signer DNSSEC** in [**DNS** > **Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) only replaces the first step in [1. Set up Cloudflare zone](#1-set-up-cloudflare-zone). You still have to follow the rest of this tutorial to complete the setup.
19+
- Enabling **DNSSEC** and **Multi-signer DNSSEC** on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page only replaces the first step in [1. Set up Cloudflare zone](#1-set-up-cloudflare-zone). You still have to follow the rest of this tutorial to complete the setup.
2020

2121
## 1. Set up Cloudflare zone
2222

@@ -26,16 +26,18 @@ If you use Cloudflare as a primary DNS provider, meaning that you manage your DN
2626

2727
<Tabs syncKey="dashPlusAPI">
2828
<TabItem label="Dashboard">
29-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone.
30-
2. Go to **DNS** > **Settings**.
31-
3. Select **Enable DNSSEC** and **Confirm**.
29+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
30+
31+
<DashButton url="/?to=/:account/:zone/dns/settings" />
32+
33+
2. Select **Enable DNSSEC** and **Confirm**.
3234

3335
:::note
3436
For the purpose of this tutorial, you will update your registrar with the DS record later, in [Step 3](/dns/dnssec/multi-signer-dnssec/setup/#3-set-up-registrar).
3537
:::
3638

37-
4. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**.
38-
5. Go to **DNS** > **Records** and create the following records at your zone apex (meaning you should use `@` in the record **Name** field):
39+
3. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**.
40+
4. Go to the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page and create the following records at your zone apex (meaning you should use `@` in the record **Name** field):
3941
- A [DNSKEY record](/dns/manage-dns-records/reference/dns-record-types/#ds-and-dnskey) with the zone signing key(s) (ZSKs) of your external provider(s).
4042
- An [NS record](/dns/manage-dns-records/reference/dns-record-types/#ns) with your external provider nameservers.
4143

@@ -108,17 +110,19 @@ If you use Cloudflare as a secondary DNS provider, do the following:
108110
<Tabs syncKey="dashPlusAPI">
109111
<TabItem label="Dashboard">
110112

111-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone.
112-
2. Go to **DNS** > **Settings**.
113-
3. For **DNSSEC with Secondary DNS** select **Live signing**.
113+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
114+
115+
<DashButton url="/?to=/:account/:zone/dns/settings" />
116+
117+
2. For **DNSSEC with Secondary DNS** select **Live signing**.
114118

115119
:::note
116120
For the purpose of this tutorial, you will update your registrar with the DS record later, in [Step 3](/dns/dnssec/multi-signer-dnssec/setup/#3-set-up-registrar).
117121
:::
118122

119-
4. Also enable **Multi-signer DNSSEC**.
120-
5. Add the zone signing key(s) (ZSKs) of your external provider(s) to a DNSKEY record at your primary DNS provider. This record should be transferred successfully to Cloudflare.
121-
6. Add your external provider(s) nameservers as NS records on your zone apex at your primary DNS provider. These records should be transferred successfully to Cloudflare.
123+
3. Also enable **Multi-signer DNSSEC**.
124+
4. Add the zone signing key(s) (ZSKs) of your external provider(s) to a DNSKEY record at your primary DNS provider. This record should be transferred successfully to Cloudflare.
125+
5. Add your external provider(s) nameservers as NS records on your zone apex at your primary DNS provider. These records should be transferred successfully to Cloudflare.
122126

123127
</TabItem>
124128
<TabItem label="API">
@@ -164,6 +168,6 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
164168

165169
## 3. Set up registrar
166170

167-
1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [dashboard](https://dash.cloudflare.com/?to=/:account/:zone/dns) by going to **DNS** > **Settings** > **DS Record**.
171+
1. Add DS records to your registrar, one for each provider. You can see your Cloudflare DS record on the [**DNS Settings**](https://dash.cloudflare.com/?to=/:account/:zone/dns/settings) page, under **DS Record**.
168172

169173
2. Update the nameserver settings at your registrar to include the nameservers of all providers you will be using for your multi-signer DNSSEC setup.

src/content/docs/dns/foundation-dns/setup.mdx

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,7 @@ import {
1313
Render,
1414
Details,
1515
Example,
16+
DashButton,
1617
} from "~/components";
1718

1819
Advanced nameservers included with [Foundation DNS](/dns/foundation-dns/) are an opt-in configuration.
@@ -78,10 +79,12 @@ To enable advanced nameservers on an existing zone:
7879
1. Opt for advanced nameservers on your zone:
7980

8081
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
81-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
82-
2. Go to **DNS** > **Records**.
83-
3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
84-
4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
82+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
83+
84+
<DashButton url="/?to=/:account/:zone/dns/records" />
85+
86+
2. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
87+
3. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
8588

8689
</TabItem> <TabItem label="API">
8790

src/content/docs/dns/manage-dns-records/how-to/batch-record-changes.mdx

Lines changed: 9 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 10
66
---
77

8-
import { GlossaryTooltip, Example, Render } from "~/components";
8+
import { GlossaryTooltip, Example, Render, DashButton } from "~/components";
99

1010
Cloudflare allows you to apply several changes to your zone records in just one action. You can [use the dashboard](#use-the-dashboard) to delete DNS records or update their <GlossaryTooltip term="proxy status">proxy status</GlossaryTooltip> in bulk, or [use the API](#use-the-api) to perform further batched operations.
1111

@@ -34,7 +34,10 @@ The number of records that you can operate with in one action depends on your zo
3434

3535
<Render file="mix-proxied-and-unproxied" product="dns" />
3636

37-
1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records).
37+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
38+
39+
<DashButton url="/?to=/:account/:zone/dns/records" />
40+
3841
2. Select the DNS records you want to set the proxy status for. Note that only `A`, `AAAA`, and `CNAME` records can be proxied.
3942
3. Select **Edit records**.
4043
4. Choose the proxy status you want to apply to the selected records.
@@ -62,7 +65,10 @@ Deleting DNS records can cause downtime and cannot be reverted. Make sure you on
6265

6366
:::
6467

65-
1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records).
68+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
69+
70+
<DashButton url="/?to=/:account/:zone/dns/records" />
71+
6672
2. Select the DNS records you want to delete.
6773
3. Select **Delete records**.
6874
4. In the **Delete DNS records** prompt, type in `DELETE` and select **Delete** to confirm.

src/content/docs/dns/manage-dns-records/how-to/create-dns-records.mdx

Lines changed: 23 additions & 17 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 2
66
---
77

8-
import { GlossaryTooltip, Render, TabItem, Tabs, Details } from "~/components";
8+
import { GlossaryTooltip, Render, TabItem, Tabs, Details, DashButton } from "~/components";
99

1010
Consider the sections below for step-by-step instructions on managing DNS records at Cloudflare.
1111

@@ -21,15 +21,17 @@ If your domain is added to Cloudflare by a hosting partner, manage your DNS reco
2121

2222
To create a DNS record in the dashboard:
2323

24-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
25-
2. Go to **DNS** > **Records**.
26-
3. Select **Add record**.
27-
4. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/).
28-
5. Complete the required fields, which vary per record. Particularly important fields (for some records) include:
24+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
25+
26+
<DashButton url="/?to=/:account/:zone/dns/records" />
27+
28+
2. Select **Add record**.
29+
3. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/).
30+
4. Complete the required fields, which vary per record. Particularly important fields (for some records) include:
2931
- **Proxy status**: For `A`, `AAAA`, and `CNAME` records, decide whether hostname traffic is <GlossaryTooltip term="proxy status" link="/dns/proxy-status/">proxied through Cloudflare</GlossaryTooltip>.
3032
- **TTL**: Short for [_Time to Live_](/dns/manage-dns-records/reference/ttl/), this field controls how long each record is valid and — as a result — how long it takes for record updates to reach your end users.
3133
- **Comment** and **Tag**: [Record attributes](/dns/manage-dns-records/reference/record-attributes/) meant for your reference.
32-
6. Select **Save**.
34+
5. Select **Save**.
3335

3436
</TabItem>
3537

@@ -49,11 +51,13 @@ For specific API examples, refer to [DNS record types](/dns/manage-dns-records/r
4951

5052
To edit DNS records in the dashboard:
5153

52-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
53-
2. Go to **DNS** > **Records**.
54-
3. On a specific record, select **Edit**.
55-
4. Make any necessary changes.
56-
5. Select **Save**.
54+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
55+
56+
<DashButton url="/?to=/:account/:zone/dns/records" />
57+
58+
2. On a specific record, select **Edit**.
59+
3. Make any necessary changes.
60+
4. Select **Save**.
5761

5862
</TabItem>
5963

@@ -71,11 +75,13 @@ To update part of a record with the API, use a [PATCH request](/api/resources/dn
7175

7276
To delete DNS records in the dashboard:
7377

74-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
75-
2. Go to **DNS** > **Records**.
76-
3. On a specific record, select **Edit**.
77-
4. Select **Delete**.
78-
5. Select **Delete** again to confirm.
78+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
79+
80+
<DashButton url="/?to=/:account/:zone/dns/records" />
81+
82+
2. On a specific record, select **Edit**.
83+
3. Select **Delete**.
84+
4. Select **Delete** again to confirm.
7985

8086
</TabItem>
8187

src/content/docs/dns/manage-dns-records/how-to/import-and-export.mdx

Lines changed: 14 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,7 @@ sidebar:
55
order: 9
66
---
77

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

1010
Use import and export to have more control over your DNS records and make processes like migrating a domain or bulk editing [record comments](/dns/manage-dns-records/reference/record-attributes/) easier.
1111

@@ -28,11 +28,13 @@ If you are using certain record types — for example, `CNAME`, `DNAME`, `MX`, `
2828

2929
To import a zone file using the dashboard:
3030

31-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
32-
2. Go to **DNS** > **Records**.
33-
3. Select **Import and Export**.
34-
4. For **Import DNS records**, select your [formatted file](#format-your-zone-file).
35-
5. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**.
31+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
32+
33+
<DashButton url="/?to=/:account/:zone/dns/records" />
34+
35+
2. Select **Import and Export**.
36+
3. For **Import DNS records**, select your [formatted file](#format-your-zone-file).
37+
4. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**.
3638

3739
</TabItem> <TabItem label="API">
3840

@@ -58,10 +60,12 @@ You can also bulk export records from Cloudflare.
5860

5961
To export records using the dashboard:
6062

61-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
62-
2. Go to **DNS** > **Records**.
63-
3. Select **Import and Export**.
64-
4. Select **Export**.
63+
1. In the Cloudflare dashboard, go to the **DNS Records** page.
64+
65+
<DashButton url="/?to=/:account/:zone/dns/records" />
66+
67+
2. Select **Import and Export**.
68+
3. Select **Export**.
6569

6670
</TabItem> <TabItem label="API">
6771

0 commit comments

Comments
 (0)