Skip to content

Commit efe0ece

Browse files
First pass with find and replace
1 parent 87c5526 commit efe0ece

File tree

6 files changed

+6
-6
lines changed

6 files changed

+6
-6
lines changed

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ For zones on paid plans, you can choose to flatten all CNAME records. This optio
3535

3636
</TabItem> <TabItem label="API">
3737

38-
Make a `PATCH` request to the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint and set `flatten_all_cnames` to `true` in the request body.
38+
Make a `PATCH` request to the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint and set `flatten_all_cnames` to `true` in the request body.
3939

4040
</TabItem> </Tabs>
4141

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ To enable advanced nameservers on an existing zone:
2525

2626
</TabItem> <TabItem label="API">
2727

28-
Use the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to send a PATCH request like the following:
28+
Use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to send a PATCH request like the following:
2929

3030
<APIRequest
3131
path="/zones/{zone_id}/dns_settings"

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -92,7 +92,7 @@ Cloudflare will assign an IPv4 and an IPv6 address to each ACNS name, and these
9292
</TabItem>
9393
<TabItem label="API">
9494

95-
Use the endpoint [Update DNS Settings for a Zone](/api/resources/dns/subresources/settings/methods/edit/) and configure the `nameservers` object accordingly for each zone.
95+
Use the endpoint [Update DNS Settings for a Zone](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) and configure the `nameservers` object accordingly for each zone.
9696

9797
</TabItem>
9898
</Tabs>

src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ Follow the steps below to achieve this conversion.
1818

1919
1. [Export a zone file](/dns/manage-dns-records/how-to/import-and-export/#export-records).
2020
2. Import the zone file into your new primary DNS provider.
21-
3. At your Cloudflare zone, use the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to enable [secondary DNS overrides](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/). Set the value for `secondary_overrides` to `true`.
21+
3. At your Cloudflare zone, use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to enable [secondary DNS overrides](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/). Set the value for `secondary_overrides` to `true`.
2222

2323
:::note
2424
Enabling secondary DNS overrides is necessary in case you have DNS records that you wish to keep <GlossaryTooltip term="proxy status" link="/dns/proxy-status/">proxied</GlossaryTooltip>.

src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -87,7 +87,7 @@ Final records adjusted in the zone file:
8787
<Render file="zone-file-size-limit" /> Existing and already proxied records
8888
will not be overwritten by the import.
8989

90-
2. Use the [Update DNS Settings endpoint](/api/resources/dns/subresources/settings/methods/edit/) with `secondary_overrides` set to `true`, to enable Secondary DNS Override.
90+
2. Use the [Update DNS Settings endpoint](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) with `secondary_overrides` set to `true`, to enable Secondary DNS Override.
9191

9292
:::caution
9393

src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ Follow the steps below to achieve this conversion.
2727
- If you have [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/), confirm each record has the appropriate setting (**Proxied** or **DNS only**).
2828
- If [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/) is disabled, make sure all of your DNS records are listed as **DNS only**.
2929

30-
3. (Optional) For consistency, use the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to specify SOA record fields according to your needs. Once Cloudflare automatically generates an SOA record for your zone on full setup, the field overrides will be considered.
30+
3. (Optional) For consistency, use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to specify SOA record fields according to your needs. Once Cloudflare automatically generates an SOA record for your zone on full setup, the field overrides will be considered.
3131

3232
## 3. Convert your zone
3333

0 commit comments

Comments
 (0)