From dc69bf9033fc786070377292a0d39b3db1412b5d Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Apr 2025 10:01:01 +0100 Subject: [PATCH 1/3] Fix URL for view creation --- src/content/docs/dns/internal-dns/dns-views.mdx | 2 +- src/content/docs/dns/internal-dns/get-started.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/dns/internal-dns/dns-views.mdx b/src/content/docs/dns/internal-dns/dns-views.mdx index 64a2018e7dab5fd..e253e465a4ce7f9 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -20,7 +20,7 @@ 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 diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index 7bbba2b8687f29c..32eabb0299da976 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -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.
From f2bd3d4ffcd7f363214902496ed9e35640b64b00 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Apr 2025 10:14:09 +0100 Subject: [PATCH 2/3] Fix URLs for other view actions --- src/content/docs/dns/internal-dns/dns-views.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/dns/internal-dns/dns-views.mdx b/src/content/docs/dns/internal-dns/dns-views.mdx index e253e465a4ce7f9..1b93301ee61ce92 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -24,7 +24,7 @@ Use the [Create Internal DNS View](/api/resources/dns/subresources/settings/subr ## 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. @@ -32,6 +32,6 @@ It is also possible to delete a DNS view that is being referenced by a Gateway r ## 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`) \ No newline at end of file +- [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`) \ No newline at end of file From ac94b66d7fadd7296d56644f21a32cc484c72ab8 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Apr 2025 10:27:17 +0100 Subject: [PATCH 3/3] Fix API link for Update DNS zone action --- src/content/docs/dns/internal-dns/get-started.mdx | 2 +- .../docs/dns/internal-dns/internal-zones/reference-zones.mdx | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index 32eabb0299da976..1f29d0600b74be0 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/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/). diff --git a/src/content/docs/dns/internal-dns/internal-zones/reference-zones.mdx b/src/content/docs/dns/internal-dns/internal-zones/reference-zones.mdx index 190a42b633bdab8..8433d484ac47442 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/reference-zones.mdx +++ b/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`.