Skip to content

Commit b9c1030

Browse files
Replace DNSSEC status and multi-provider setting
1 parent d23fd2b commit b9c1030

File tree

3 files changed

+17
-24
lines changed

3 files changed

+17
-24
lines changed

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

Lines changed: 9 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ head:
99
content: Set up multi-signer DNSSEC with outgoing zone transfers
1010
---
1111

12-
import { Example } from "~/components";
12+
import { Example, APIRequest } from "~/components";
1313

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

@@ -27,17 +27,14 @@ Note that:
2727

2828
1. Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/methods/edit/) to enable DNSSEC and activate multi-signer DNSSEC for your zone. This is done by setting `status` to `active` and `dnssec_multi_signer` to `true`, as in the following example.
2929

30-
```bash
31-
curl --request PATCH \
32-
'https://api.cloudflare.com/client/v4/zones/{zone_id}/dnssec' \
33-
--header "X-Auth-Email: <EMAIL>" \
34-
--header "X-Auth-Key: <API_KEY>" \
35-
--header "Content-Type: application/json" \
36-
--data '{
37-
"status": "active",
38-
"dnssec_multi_signer": true
39-
}'
40-
```
30+
<APIRequest
31+
path="/zones/{zone_id}/dnssec"
32+
method="PATCH"
33+
json={{
34+
"status": "active",
35+
"dnssec_multi_signer": true,
36+
}}
37+
/>
4138

4239
2. Add the ZSK(s) of your external provider(s) to Cloudflare by creating a DNSKEY record on your zone.
4340

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

Lines changed: 8 additions & 11 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 } from "~/components";
11+
import { Render, TabItem, Tabs, APIRequest } 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

@@ -137,16 +137,13 @@ If your account [zone defaults](/dns/additional-options/dns-zone-defaults/) are
137137

138138
Send the following `PATCH` request replacing the placeholders with your zone ID and authentication information:
139139

140-
```bash
141-
curl --request PATCH \
142-
"https://api.cloudflare.com/client/v4/zones/{zone_id}/dns_settings" \
143-
--header "X-Auth-Email: <EMAIL>" \
144-
--header "X-Auth-Key: <API_KEY>" \
145-
--header "Content-Type: application/json" \
146-
--data '{
147-
"multi_provider": true
148-
}'
149-
```
140+
<APIRequest
141+
path="/zones/{zone_id}/dns_settings"
142+
method="PATCH"
143+
json={{
144+
"multi_provider": true,
145+
}}
146+
/>
150147

151148
</TabItem> </Tabs>
152149

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

Lines changed: 0 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,6 @@ Use the [Edit DNSSEC Status endpoint](/api/resources/dns/subresources/dnssec/met
100100
}}
101101
/>
102102

103-
104103
</TabItem> </Tabs>
105104

106105
3. Make sure Cloudflare nameservers are added at your registrar. You can see your Cloudflare nameservers on the dashboard by going to **DNS** > **Records**.

0 commit comments

Comments
 (0)