[DNS] Use DashButton zone level

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

@@ -6,7 +6,7 @@ sidebar:
 
 ---
 
-import { FeatureTable, Details } from "~/components"
+import { FeatureTable, Details, DashButton } from "~/components"
 
 When you use Cloudflare DNS, you can access data about DNS queries through a variety of sources.
 
@@ -28,8 +28,7 @@ When using GraphQL, you also have the option to get data for DNS queries across
 
 For a quick summary, view your DNS analytics on the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-2. Go to **DNS** > **Analytics**.
+<DashButton url="/?to=/:account/:zone/dns/analytics" />
 
 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.
 

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

@@ -11,7 +11,7 @@ import { DashButton } from "~/components";
 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.
 
 :::caution
-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.
+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.
 :::
 
 ## Steps

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

@@ -5,7 +5,7 @@ sidebar:
   order: 5
 ---
 
-import { Details, Example } from "~/components"
+import { Details, Example, DashButton } from "~/components"
 
 If you control your own IP prefix(es), you can set up reverse zones with PTR records to allow reverse DNS lookups.
 
@@ -71,7 +71,9 @@ To set up a reverse zone, you need to create a reverse DNS zone and add PTR reco
 
 ### 2. Add PTR records
 
-1. Go to **DNS** > **Records**.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
 
 2. For each IP within the prefix, add a PTR record using the least significant octet(s) as the subdomain.
 

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

@@ -8,7 +8,7 @@ head:
     content: Set up CNAME flattening
 ---
 
-import { Render, TabItem, Tabs, GlossaryTooltip } from "~/components";
+import { Render, TabItem, Tabs, GlossaryTooltip, DashButton } from "~/components";
 
 :::note
 
@@ -26,9 +26,11 @@ For zones on paid plans, you can choose to flatten all CNAME records. This optio
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-2. Go to **DNS** > **Settings**.
-3. Turn on the option **CNAME flattening for all CNAME records**.
+1. In the Cloudflare dashboard, go to the **DNS Settings** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/settings" />
+
+2. Turn on the option **CNAME flattening for all CNAME records**.
 
 </TabItem> <TabItem label="API">
 
@@ -49,11 +51,10 @@ If you use this option, a special [tag](/dns/manage-dns-records/reference/record
 
 <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-2. In **DNS** > **Settings**, make sure that **CNAME flattening for all CNAME records** is turned off.
-3. Go to **DNS** > **Records** and find the CNAME record you would like to flatten.
-4. Select **Edit** and turn on the **Flatten** option.
-5. Select **Save** to confirm.
+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.
+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.
+3. Select **Edit** and turn on the **Flatten** option.
+4. Select **Save** to confirm.
 
 :::note[Unavailable flatten option]
 For the following cases, **Flatten** will not be available:

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

@@ -36,7 +36,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the
 
    To import the zone file using the API, refer to the [Import DNS Records endpoint](/api/resources/dns/subresources/records/methods/import/).
 
-3. Go to **DNS** > **Settings**, and select **Enable DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
+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/).
 
 <APIRequest
 	path="/zones/{zone_id}/dnssec"
@@ -46,7 +46,7 @@ The provider you are migrating from must allow you to add DNSKEY records on the
 	}}
 />
 
-4. Go to **DNS** > **Settings**, and enable **Multi-signer DNSSEC**. Or use the following [API request](/api/resources/dns/subresources/dnssec/methods/edit/).
+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/).
 
 <APIRequest
 	path="/zones/{zone_id}/dnssec"
@@ -135,8 +135,8 @@ multisigner.info.    3600    IN    DNSKEY    256 3 13 pxEU<bla_bla_bla>0xOg==
 
 ## 3. Set up registrar
 
-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**.
-2. Add Cloudflare assigned nameservers to your registrar. You can see your Cloudflare nameservers by going to **DNS** > **Records**.
+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**.
+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
 
 At this point your zone is in a [multi-signer DNSSEC setup](/dns/dnssec/multi-signer-dnssec/).
 

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

@@ -6,7 +6,7 @@ sidebar:
   label: Setup
 ---
 
-import { Tabs, TabItem, APIRequest } from "~/components";
+import { Tabs, TabItem, APIRequest, DashButton } from "~/components";
 
 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).
 
@@ -16,7 +16,7 @@ Note that:
 
 - This process requires that your other DNS provider(s) also support multi-signer DNSSEC.
 - Although you can complete a few steps via the dashboard, currently the whole process can only be completed using the API.
-- 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.
+- 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.
 
 ## 1. Set up Cloudflare zone
 
@@ -26,16 +26,18 @@ If you use Cloudflare as a primary DNS provider, meaning that you manage your DN
 
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone.
-2. Go to **DNS** > **Settings**.
-3. Select **Enable DNSSEC** and **Confirm**.
+1. In the Cloudflare dashboard, go to the **DNS Settings** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/settings" />
+
+2. Select **Enable DNSSEC** and **Confirm**.
 
 :::note
 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).
 :::
 
-4. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**.
-5. Go to **DNS** > **Records** and create the following records at your zone apex (meaning you should use `@` in the record **Name** field):
+3. Also enable **Multi-signer DNSSEC** and **Multi-provider DNS**.
+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):
     - 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).
     - An [NS record](/dns/manage-dns-records/reference/dns-record-types/#ns) with your external provider nameservers.
 
@@ -108,17 +110,19 @@ If you use Cloudflare as a secondary DNS provider, do the following:
 <Tabs syncKey="dashPlusAPI">
 <TabItem label="Dashboard">
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone.
-2. Go to **DNS** > **Settings**.
-3. For **DNSSEC with Secondary DNS** select **Live signing**.
+1. In the Cloudflare dashboard, go to the **DNS Settings** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/settings" />
+
+2. For **DNSSEC with Secondary DNS** select **Live signing**.
 
 :::note
 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).
 :::
 
-4. Also enable **Multi-signer DNSSEC**.
-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.
-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.
+3. Also enable **Multi-signer DNSSEC**.
+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.
+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.
 
 </TabItem>
 <TabItem label="API">
@@ -164,6 +168,6 @@ $ dig <ZONE_NAME> dnskey @<CLOUDFLARE_NAMESERVER> +noall +answer | grep 256
 
 ## 3. Set up registrar
 
-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**.
+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**.
 
 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

@@ -13,6 +13,7 @@ import {
 	Render,
 	Details,
 	Example,
+	DashButton,
 } from "~/components";
 
 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:
 1. Opt for advanced nameservers on your zone:
 
    <Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
-   1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
-   2. Go to **DNS** > **Records**.
-   3. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
-   4. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
+   1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+      <DashButton url="/?to=/:account/:zone/dns/records" />
+
+   2. In the **Cloudflare nameservers** card, enable **Advanced nameservers**.
+   3. After you refresh the page, the card will display the values for your advanced nameservers `NS` records.
 
    </TabItem> <TabItem label="API">
 

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

@@ -5,7 +5,7 @@ sidebar:
   order: 10
 ---
 
-import { GlossaryTooltip, Example, Render } from "~/components";
+import { GlossaryTooltip, Example, Render, DashButton } from "~/components";
 
 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.
 
@@ -34,7 +34,10 @@ The number of records that you can operate with in one action depends on your zo
 
 <Render file="mix-proxied-and-unproxied" product="dns" />
 
-1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records).
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
 2. Select the DNS records you want to set the proxy status for. Note that only `A`, `AAAA`, and `CNAME` records can be proxied.
 3. Select **Edit records**.
 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
 
 :::
 
-1. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records).
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
 2. Select the DNS records you want to delete.
 3. Select **Delete records**.
 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

@@ -5,7 +5,7 @@ sidebar:
   order: 2
 ---
 
-import { GlossaryTooltip, Render, TabItem, Tabs, Details } from "~/components";
+import { GlossaryTooltip, Render, TabItem, Tabs, Details, DashButton } from "~/components";
 
 Consider the sections below for step-by-step instructions on managing DNS records at Cloudflare.
 
@@ -21,15 +21,17 @@ If your domain is added to Cloudflare by a hosting partner, manage your DNS reco
 
 To create a DNS record in the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
-2. Go to **DNS** > **Records**.
-3. Select **Add record**.
-4. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/).
-5. Complete the required fields, which vary per record. Particularly important fields (for some records) include:
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. Select **Add record**.
+3. Choose a record [**Type**](/dns/manage-dns-records/reference/dns-record-types/).
+4. Complete the required fields, which vary per record. Particularly important fields (for some records) include:
    - **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>.
    - **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.
    - **Comment** and **Tag**: [Record attributes](/dns/manage-dns-records/reference/record-attributes/) meant for your reference.
-6. Select **Save**.
+5. Select **Save**.
 
 </TabItem>
 
@@ -49,11 +51,13 @@ For specific API examples, refer to [DNS record types](/dns/manage-dns-records/r
 
 To edit DNS records in the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
-2. Go to **DNS** > **Records**.
-3. On a specific record, select **Edit**.
-4. Make any necessary changes.
-5. Select **Save**.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. On a specific record, select **Edit**.
+3. Make any necessary changes.
+4. Select **Save**.
 
 </TabItem>
 
@@ -71,11 +75,13 @@ To update part of a record with the API, use a [PATCH request](/api/resources/dn
 
 To delete DNS records in the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account and domain.
-2. Go to **DNS** > **Records**.
-3. On a specific record, select **Edit**.
-4. Select **Delete**.
-5. Select **Delete** again to confirm.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. On a specific record, select **Edit**.
+3. Select **Delete**.
+4. Select **Delete** again to confirm.
 
 </TabItem>
 

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

@@ -5,7 +5,7 @@ sidebar:
   order: 9
 ---
 
-import { Render, TabItem, Tabs, APIRequest } from "~/components";
+import { Render, TabItem, Tabs, APIRequest, DashButton } from "~/components";
 
 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.
 
@@ -28,11 +28,13 @@ If you are using certain record types — for example, `CNAME`, `DNAME`, `MX`, `
 
 To import a zone file using the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
-2. Go to **DNS** > **Records**.
-3. Select **Import and Export**.
-4. For **Import DNS records**, select your [formatted file](#format-your-zone-file).
-5. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. Select **Import and Export**.
+3. For **Import DNS records**, select your [formatted file](#format-your-zone-file).
+4. If you do not want [applicable records](/dns/proxy-status/) proxied, unselect **Proxy imported DNS records**.
 
 </TabItem> <TabItem label="API">
 
@@ -58,10 +60,12 @@ You can also bulk export records from Cloudflare.
 
 To export records using the dashboard:
 
-1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
-2. Go to **DNS** > **Records**.
-3. Select **Import and Export**.
-4. Select **Export**.
+1. In the Cloudflare dashboard, go to the **DNS Records** page.
+
+   <DashButton url="/?to=/:account/:zone/dns/records" />
+
+2. Select **Import and Export**.
+3. Select **Export**.
 
 </TabItem> <TabItem label="API">
 

src/content/docs/dns/manage-dns-records/how-to/subdomains-outside-cloudflare.mdx

@@ -35,7 +35,7 @@ To delegate a subdomain such as *internal.example.com*, tell DNS resolvers wher
 
 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account.
 2. Select the domain that contains the subdomain to be delegated.
-3. Go to **DNS** > **Records**.
+3. Go to [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records).
 4. Create `NS` records for the subdomain. For example:
    * `internal.example.com NS ns1.externalhost.com`
    * `internal.example.com NS ns2.externalhost.com`