Skip to content

Commit bab33e1

Browse files
Third batch, excluding zone-conversion files that needed edits
1 parent 5257b67 commit bab33e1

File tree

4 files changed

+25
-18
lines changed

4 files changed

+25
-18
lines changed

src/content/docs/dns/zone-setups/full-setup/setup.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ description: >-
1010
If you want to use Cloudflare as your primary DNS provider and manage your DNS records, your domain should be using a full setup.
1111
---
1212

13-
import { Render } from "~/components";
13+
import { Render, DashButton } from "~/components";
1414

1515
<Render file="full-setup-definition" product="dns" />
1616

@@ -64,8 +64,11 @@ When you start using Cloudflare's nameservers for authoritative DNS and your zon
6464

6565
### Get nameserver names
6666

67-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com) and select your account and domain.
68-
2. On **Overview**, locate the nameserver names in **2. Replace with Cloudflare's nameservers**.
67+
1. In the Cloudflare dashboard, go to the zone **Overview** page.
68+
69+
<DashButton url="/?to=/:account/:zone/" />
70+
71+
2. Locate the nameserver names in **2. Replace with Cloudflare's nameservers**.
6972

7073
![Find nameserver names on the Overview page of your domain](~/assets/images/dns/nameserver-names.png)
7174

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

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -81,12 +81,13 @@ If you previously [created a peer DNS server](#2-create-peer-dns-server-optional
8181

8282
To link a primary zone to a peer using the dashboard:
8383

84-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login).
85-
2. Select your account and zone.
86-
3. Go to **DNS** > **Settings**.
87-
4. For **DNS Zone Transfers**, select **Manage linked peers**.
88-
5. Select a peer.
89-
6. Select **Save**.
84+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
85+
86+
<DashButton url="/?to=/:account/:zone/dns/settings" />
87+
88+
2. For **DNS Zone Transfers**, select **Manage linked peers**.
89+
3. Select a peer.
90+
4. Select **Save**.
9091

9192
</TabItem> <TabItem label="API">
9293

src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary.mdx

Lines changed: 5 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -14,6 +14,7 @@ import {
1414
Tabs,
1515
GlossaryTooltip,
1616
APIRequest,
17+
DashButton,
1718
} from "~/components";
1819

1920
[DNS Security Extensions (DNSSEC)](https://www.cloudflare.com/learning/dns/dns-security/) increase security by adding cryptographic signatures to DNS records. When you use multiple providers and Cloudflare is secondary, you have a few options to enable DNSSEC for records served by Cloudflare.
@@ -38,13 +39,13 @@ In this setup, DNSSEC on your pirmary DNS provider does not need to be enabled.
3839

3940
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
4041

41-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone.
42+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
4243

43-
2. Go to **DNS** > **Settings**.
44+
<DashButton url="/?to=/:account/:zone/dns/settings" />
4445

45-
3. Under **DNSSEC with Secondary DNS** select **Live signing**. You will then have access to several necessary values to create a **DS** record at your registrar.
46+
2. Under **DNSSEC with Secondary DNS** select **Live signing**. You will then have access to several necessary values to create a **DS** record at your registrar.
4647

47-
4. <Render file="dnssec-registrar-steps" product="dns" />
48+
3. <Render file="dnssec-registrar-steps" product="dns" />
4849

4950
</TabItem> <TabItem label="API">
5051

src/content/docs/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic.mdx

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ head:
88
content: Proxy traffic with Secondary DNS override
99
---
1010

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

1313
When you set up [incoming zone transfers](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/) on a secondary zone, you cannot enable the proxy on any transferred DNS records by default.
1414

@@ -38,10 +38,12 @@ Before you set up Secondary DNS override, make sure that you have:
3838

3939
<Tabs syncKey="dashPlusAPI"> <TabItem label="Dashboard">
4040

41-
1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and domain.
42-
2. Go to **DNS** > **Settings**.
43-
3. Enable **Secondary DNS override**.
44-
4. On **DNS** > **Records**, for specific A, AAAA, or CNAME records, select the grey cloud icon to set their **Proxy status** to **Proxied**.
41+
1. In the Cloudflare dashboard, go to the **DNS Settings** page.
42+
43+
<DashButton url="/?to=/:account/:zone/dns/settings" />
44+
45+
2. Enable **Secondary DNS override**.
46+
3. On the [**DNS Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) page, for specific A, AAAA, or CNAME records, select the grey cloud icon to set their **Proxy status** to **Proxied**.
4547

4648
</TabItem> <TabItem label="API">
4749

0 commit comments

Comments
 (0)