[DNS] Fix API docs links for internal DNS actions (#21286)

* Fix URL for view creation

* Fix URLs for other view actions

* Fix API link for Update DNS zone action

Author: RebeccaTamachiro

src/content/docs/dns/internal-dns/dns-views.mdx

@@ -20,18 +20,18 @@ When setting up DNS views, observe the following conditions:
 
 ## Create a view
 
-Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subresources/views/methods/create/) endpoint. For each view you create, list all the internal zones that should be grouped under that view.
+Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/create/) endpoint. For each view you create, list all the internal zones that should be grouped under that view.
 
 ## Delete a view
 
-Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subresources/views/methods/delete/) endpoint.
+Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/delete/) endpoint.
 
 DNS views can be deleted even if they still have internal zones linked to them. The internal DNS zones will continue to exist but will be unlinked once the view is deleted.
 
 It is also possible to delete a DNS view that is being referenced by a Gateway resolver policy. In this case, queries matching the policy will return SERVFAIL.
 
 ## Other actions
 
-- [Update a DNS view](/api/resources/dns/subresources/settings/subresources/views/methods/edit/) (`PATCH`)
-- [Get view details](/api/resources/dns/subresources/settings/subresources/views/methods/get/) (`GET`)
-- [List DNS views](/api/resources/dns/subresources/settings/subresources/views/methods/list/) (`GET`)
+- [Update a DNS view](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/edit/) (`PATCH`)
+- [Get view details](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/get/) (`GET`)
+- [List DNS views](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/list/) (`GET`)

src/content/docs/dns/internal-dns/get-started.mdx

@@ -47,7 +47,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 ### (Optional) Reference a zone from another zone
 
-1. Use the [Update DNS settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint to add a reference from an internal zone to another internal zone. In `--data`, specify the `internal_dns` object with the parameter `reference_zone_id`. For details, refer to [reference zones](/dns/internal-dns/internal-zones/reference-zones/).
+1. Use the [Update DNS settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint to add a reference from an internal zone to another internal zone. In `--data`, specify the `internal_dns` object with the parameter `reference_zone_id`. For details, refer to [reference zones](/dns/internal-dns/internal-zones/reference-zones/).
 
 <Example>
 <Render file="internal-reference-zone-api"/>
@@ -57,7 +57,7 @@ Although there are some steps that can be achieved on the dashboard, currently t
 
 Since the resolver policy will require a [DNS view](/dns/internal-dns/dns-views/), you must have at least one view to be able to route requests to internal zones.
 
-1. Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subresources/views/methods/create/) endpoint. For each view you create, list all the internal zones that should be grouped under that view.
+1. Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/create/) endpoint. For each view you create, list all the internal zones that should be grouped under that view.
 
 <Details header="DNS view configuration conditions">
 <Render file="internal-dns-view-conditions" />

src/content/docs/dns/internal-dns/internal-zones/reference-zones.mdx

@@ -22,7 +22,7 @@ A wildcard record (`*.example.local`) in the matching internal zone will take pr
 
 ## Set up
 
-To set up a reference zone, use the [Update DNS settings](/api/resources/dns/subresources/settings/methods/edit/) endpoint. In `--data`, specify the `internal_dns` object with the parameter `reference_zone_id`.
+To set up a reference zone, use the [Update DNS settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint. In `--data`, specify the `internal_dns` object with the parameter `reference_zone_id`.
 
 <Example>
 <Render file="internal-reference-zone-api"/>