[DNS] DNS Settings API endpoint link review (cloudflare#22853)

* First pass with find and replace

* Fix deprecations yaml differentiating zone vs account

* Update links to DNS settings for account

* Fix broken link prior to review of disablement flow

* Adjust disable instructions to account for current endpoint

Author: RebeccaTamachiro

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

@@ -35,7 +35,7 @@ For zones on paid plans, you can choose to flatten all CNAME records. This optio
 
 </TabItem> <TabItem label="API">
 
-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.
+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.
 
 </TabItem> </Tabs>
 

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

@@ -25,7 +25,7 @@ To enable advanced nameservers on an existing zone:
 
     </TabItem> <TabItem label="API">
 
-    Use the [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to send a PATCH request like the following:
+    Use the [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to send a PATCH request like the following:
 
   	<APIRequest
   	path="/zones/{zone_id}/dns_settings"

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

@@ -92,7 +92,7 @@ Cloudflare will assign an IPv4 and an IPv6 address to each ACNS name, and these
 </TabItem>
 <TabItem label="API">
 
-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.
+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.
 
 </TabItem>
 </Tabs>
@@ -120,7 +120,7 @@ Refer to [DNS zone defaults](/dns/nameservers/nameserver-options/#dns-zone-defau
 </TabItem>
 <TabItem label="API">
 
-Use the endpoint [Update DNS Settings for an Account](/api/resources/dns/subresources/settings/methods/edit/). Within the `zone_defaults` object, set the following:
+Use the endpoint [Update DNS Settings for an Account](/api/resources/dns/subresources/settings/subresources/account/methods/edit/). Within the `zone_defaults` object, set the following:
 
 ```txt
 "zone_defaults": {
@@ -148,8 +148,8 @@ To remove ACNS from a zone, first update your nameservers to stop using ACNS:
 </TabItem>
 <TabItem label="API">
 
-* If you are using [Cloudflare Registrar](/registrar/), use the [Update DNS settings endpoint](/api/resources/dns/subresources/settings/methods/edit/) to change the `enabled` parameter to `false`, and then [contact Cloudflare Support](/support/contacting-cloudflare-support/) to set your nameservers back to the regular Cloudflare branded nameservers.
-* If you are not using [Cloudflare Registrar](/registrar/), modify the domain's registrar to use your regular Cloudflare branded nameservers and then use the [Update DNS settings endpoint](/api/resources/dns/subresources/settings/methods/edit/) to set the `enabled` parameter to `false`.
+* If you are using [Cloudflare Registrar](/registrar/), use the [Update DNS settings endpoint](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) to set the `type` parameter in the `nameservers` object to `"cloudflare.standard"`. Then, [contact Cloudflare Support](/support/contacting-cloudflare-support/) to set your nameservers back to the regular Cloudflare branded nameservers.
+* If you are not using [Cloudflare Registrar](/registrar/), modify the domain's registrar to use your regular Cloudflare branded nameservers and then use the [Update DNS settings endpoint](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) to set the `type` parameter in the `nameservers` object to `"cloudflare.standard"`.
 
 </TabItem>
 </Tabs>

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

@@ -57,7 +57,7 @@ If the parameter `ns_set` is omitted, the default set `1` will be assigned.
 
 2. If you are **not** using [Cloudflare Registrar](/registrar/), update the nameservers at your registrar to use the TCNS names. If you are using [Cloudflare Registrar](/registrar/), no further action is needed.
 
-To make these TCNS the default namerservers for all new zones added to your account from now on, use the endpoint [Update DNS Settings for an Account](/api/resources/dns/subresources/settings/methods/edit/). Within the `zone_defaults` object, set the following:
+To make these TCNS the default namerservers for all new zones added to your account from now on, use the endpoint [Update DNS Settings for an Account](/api/resources/dns/subresources/settings/subresources/account/methods/edit/). Within the `zone_defaults` object, set the following:
 
 ```txt
 "zone_defaults": {

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

@@ -18,7 +18,7 @@ Follow the steps below to achieve this conversion.
 
 1. [Export a zone file](/dns/manage-dns-records/how-to/import-and-export/#export-records).
 2. Import the zone file into your new primary DNS provider.
-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`.
+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`.
 
     :::note
     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

@@ -87,7 +87,7 @@ Final records adjusted in the zone file:
    <Render file="zone-file-size-limit" /> Existing and already proxied records
    will not be overwritten by the import.
 
-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.
+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.
 
 :::caution
 

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

@@ -27,7 +27,7 @@ Follow the steps below to achieve this conversion.
     - 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**).
     - 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**.
 
-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.
+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.
 
 ## 3. Convert your zone
 

src/content/release-notes/api-deprecations.yaml

@@ -40,7 +40,7 @@ entries:
     description: |-
       Deprecation date: June 8, 2025
 
-      The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated. Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
+      The Zone Settings API endpoints for managing zone-level CNAME flattening are deprecated. Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoints to manage this setting.
 
       Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Zone Settings endpoints.
 
@@ -181,7 +181,7 @@ entries:
       Deprecation date: March 14, 2025
 
       The fields `"default_nameservers"` and `"use_account_custom_ns_by_default"` within the `"settings"` object of accounts are deprecated.
-      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage this setting.
+      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/subresources/account/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/account/methods/edit/) endpoints to manage this setting.
       This setting is available in the new API as `.zone_defaults.nameservers.type`, with allowed values `"cloudflare.standard"`, `"cloudflare.standard.random"`, `"custom.account"` and `"custom.tenant"`.
 
       Changes via the old endpoints will be reflected in the new ones, and vice versa, so there is no need to migrate existing zones. However, future API calls must use DNS Settings instead of the Accounts endpoints.
@@ -384,7 +384,7 @@ entries:
 
       The dedicated endpoints for DNS settings `use_apex_ns` and `secondary_overrides` are being deprecated.
 
-      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/methods/edit/) endpoints to manage these settings.
+      Instead, use the [Show DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/get/) and [Update DNS Settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoints to manage these settings.
 
       - Instead of the `.../use_apex_ns` endpoint, use the `multi_provider` field.
       - Instead of the `.../secondary_overrides` endpoint, use the `secondary_overrides` field.