From 21848934aa59f11e58f486dc8acc4a38aa4a8a82 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 21 May 2025 16:25:40 +0100 Subject: [PATCH 01/18] Add Dash steps for internal zone creation --- .../dns/internal-dns/internal-zones/setup.mdx | 19 ++++++++++++++++++- 1 file changed, 18 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx index 9f9c667c69e425f..23a2dc0a46d1280 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx @@ -5,7 +5,7 @@ sidebar: order: 2 --- -import { Example, Render } from "~/components"; +import { Example, Render, Tabs, TabItem } from "~/components"; Refer to the following sections to learn how to manage your [internal DNS zones](/dns/internal-dns/internal-zones/). @@ -17,8 +17,25 @@ When setting up internal zones, observe the following conditions: ## Create an internal zone + + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** and select **Create an internal zone**. +3. Give your internal zone a descriptive name, observing the [configuration conditions](#configuration-conditions). +4. Add DNS records to your internal zone using your preferred option: +- [Import]((/dns/manage-dns-records/how-to/import-and-export/)) a formatted BIND file. +- Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. +:::note +Creating multiple internal DNS records in batch is currently only supported via API. +::: + + + + + + ## Other actions The API endpoints to manage internal zones are the same as for managing public zones. The main difference is that the zone type must be set to `internal`. Refer to the API documentation below for details: From 4ed1fe6dd0c6500207f1920fb4c3b980c6b6bf87 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 21 May 2025 16:47:16 +0100 Subject: [PATCH 02/18] Add tabs components and Dash steps to dns-views --- .../docs/dns/internal-dns/dns-views.mdx | 31 +++++++++++++++++-- 1 file changed, 28 insertions(+), 3 deletions(-) diff --git a/src/content/docs/dns/internal-dns/dns-views.mdx b/src/content/docs/dns/internal-dns/dns-views.mdx index 1b93301ee61ce92..d64b94b32ffaaa6 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -6,7 +6,7 @@ sidebar: label: Views --- -import { Details, Render } from "~/components"; +import { Details, Render, Tabs, TabItem } from "~/components"; Internal DNS views are logical groupings of [internal DNS zones](/dns/internal-dns/internal-zones/). As explained in the [architecture overview](/dns/internal-dns/#architecture-overview), DNS views are referenced by [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) to define how a specific query should be resolved. @@ -20,16 +20,41 @@ When setting up DNS views, observe the following conditions: ## Create a view + + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** > **Views**. +3. Give your view a descriptive name, observing the [configuration conditions](#configuration-conditions). +4. Add zones to your view by selecting **Manage zones added(TBD)**. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view and choose **Save** to confirm. + + + + 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/account/subresources/views/methods/delete/) endpoint. +## Delete a view 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. + + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** > **Views**. +3. Find the view you want to delete. +4. Select the three dots in the corresponding row and choose *Delete*. +5. In the confirmation dialog, select **Delete** again to proceed. + + + + +Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/delete/) endpoint. + + + ## Other actions - [Update a DNS view](/api/resources/dns/subresources/settings/subresources/account/subresources/views/methods/edit/) (`PATCH`) From d41b45022f891b1e24b7b3e7a6a3806f937eb0a8 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Fri, 23 May 2025 13:11:42 +0100 Subject: [PATCH 03/18] Revise create a view Dash steps --- src/content/docs/dns/internal-dns/dns-views.mdx | 6 ++++-- 1 file changed, 4 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 d64b94b32ffaaa6..8c9d4085c2ddaa4 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -24,8 +24,10 @@ When setting up DNS views, observe the following conditions: 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. 2. Go to **Internal DNS** > **Views**. -3. Give your view a descriptive name, observing the [configuration conditions](#configuration-conditions). -4. Add zones to your view by selecting **Manage zones added(TBD)**. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view and choose **Save** to confirm. +3. Select **Create a view**. +4. Give your view a descriptive name. +5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view +6. Choose **Save** to confirm. From fb0724bd42a67001cb4db70a7d36a79bfd3173b3 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Fri, 23 May 2025 13:29:25 +0100 Subject: [PATCH 04/18] Add dash instructions for reference zone assignment --- .../internal-zones/reference-zones.mdx | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-) 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 8433d484ac47442..27481815c20ad3a 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 @@ -5,7 +5,7 @@ sidebar: order: 4 --- -import { Example, Render } from "~/components"; +import { Example, Render, Tabs, TabItem } from "~/components"; During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain. @@ -22,11 +22,24 @@ 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/subresources/zone/methods/edit/) endpoint. In `--data`, specify the `internal_dns` object with the parameter `reference_zone_id`. + + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** and select a zone. +3. Within the selected zone, go to **Reference zone**. +4. Select **Add reference zone**. If your zone already has a reference zone set up, you must first remove it. As explained in the [configuration conditions](#configuration-conditions), each internal zone can only reference one other zone at a time. +5. Find the zone you want to use as reference and choose **Select** in the respective row. + + + + +Use the [Update DNS settings](/api/resources/dns/subresources/settings/subresources/zone/methods/edit/) endpoint. In `--json`, specify the `internal_dns` object with the parameter `reference_zone_id`. A third zone (C) could also point to zone B as a reference, but zone A cannot add another zone as a reference while also having zone B configured as its reference zone. - \ No newline at end of file + + + \ No newline at end of file From 3bb666bd23efd42ef50f3e5a334baf1d55024f2a Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Fri, 23 May 2025 13:57:35 +0100 Subject: [PATCH 05/18] Get-started: remove api-only and add Dash tab placeholder --- .../docs/dns/internal-dns/get-started.mdx | 28 +++++++++++++++++-- 1 file changed, 25 insertions(+), 3 deletions(-) diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index 1f29d0600b74be0..b57287a96bfa41a 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -9,15 +9,12 @@ import { TabItem, Tabs, Details, Example, Render } from "~/components"; Follow this guide to get started with Internal DNS. -Although there are some steps that can be achieved on the dashboard, currently the whole process can only be completed via API. - ## Before you begin - Make sure you have an Enterprise account with access to [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) and [Internal DNS](/dns/internal-dns/). - Consider the different ways in which you can [connect to Gateway resolver](/dns/internal-dns/connectivity/). -- If you are not familiar with how to use Cloudflare API, refer to [Fundamentals](/fundamentals/api/get-started/). - If you will be using an API token for authentication, make sure you have the following permissions:
@@ -41,28 +38,53 @@ Although there are some steps that can be achieved on the dashboard, currently t ## 1. Set up your internal DNS zone + + +(Dash instructions) + + + + + ### (Optional) Reference a zone from another zone + + +(Dash instructions) + + + 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/). + + ## 2. Link your internal zone to a view 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. + + +(Dash instructions) + + + 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.
+ + + ## 3. Configure Gateway policies :::note From 2ca66fdf0c24a7a5b3bb194a526d8308411a279b Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Fri, 23 May 2025 14:58:43 +0100 Subject: [PATCH 06/18] Fix broken link --- src/content/docs/dns/internal-dns/internal-zones/setup.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx index 23a2dc0a46d1280..849f832759a4e3a 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx @@ -23,7 +23,7 @@ When setting up internal zones, observe the following conditions: 2. Go to **Internal DNS** and select **Create an internal zone**. 3. Give your internal zone a descriptive name, observing the [configuration conditions](#configuration-conditions). 4. Add DNS records to your internal zone using your preferred option: -- [Import]((/dns/manage-dns-records/how-to/import-and-export/)) a formatted BIND file. +- [Import](/dns/manage-dns-records/how-to/import-and-export/) a formatted BIND file. - Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. :::note Creating multiple internal DNS records in batch is currently only supported via API. From cb3afe278c0c465d76750960a923e54e74cce773 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 26 May 2025 15:28:36 +0100 Subject: [PATCH 07/18] Add partial for zone creation and replace in relevant pages --- .../docs/dns/internal-dns/get-started.mdx | 6 +++-- src/content/docs/dns/internal-dns/index.mdx | 2 +- .../dns/internal-dns/internal-zones/setup.mdx | 12 ++------- ...reate.mdx => internal-zone-create-api.mdx} | 0 .../dns/internal-zone-create-dash.mdx | 26 +++++++++++++++++++ 5 files changed, 33 insertions(+), 13 deletions(-) rename src/content/partials/dns/{internal-zone-create.mdx => internal-zone-create-api.mdx} (100%) create mode 100644 src/content/partials/dns/internal-zone-create-dash.mdx diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index b57287a96bfa41a..cb463c3ebe40047 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -40,11 +40,13 @@ Follow this guide to get started with Internal DNS. -(Dash instructions) + - diff --git a/src/content/docs/dns/internal-dns/index.mdx b/src/content/docs/dns/internal-dns/index.mdx index 678cad05702fa06..b88295c2a37b2d6 100644 --- a/src/content/docs/dns/internal-dns/index.mdx +++ b/src/content/docs/dns/internal-dns/index.mdx @@ -21,7 +21,7 @@ Simplify private network management with Cloudflare DNS for your internal resour -Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to the query context, such as its source IP. +Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to the query context, such as query source IP. diff --git a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx index 849f832759a4e3a..ff84eb18c642e6a 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx @@ -19,20 +19,12 @@ When setting up internal zones, observe the following conditions: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. -2. Go to **Internal DNS** and select **Create an internal zone**. -3. Give your internal zone a descriptive name, observing the [configuration conditions](#configuration-conditions). -4. Add DNS records to your internal zone using your preferred option: -- [Import](/dns/manage-dns-records/how-to/import-and-export/) a formatted BIND file. -- Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. -:::note -Creating multiple internal DNS records in batch is currently only supported via API. -::: + - + diff --git a/src/content/partials/dns/internal-zone-create.mdx b/src/content/partials/dns/internal-zone-create-api.mdx similarity index 100% rename from src/content/partials/dns/internal-zone-create.mdx rename to src/content/partials/dns/internal-zone-create-api.mdx diff --git a/src/content/partials/dns/internal-zone-create-dash.mdx b/src/content/partials/dns/internal-zone-create-dash.mdx new file mode 100644 index 000000000000000..8a5ab14f3b7370f --- /dev/null +++ b/src/content/partials/dns/internal-zone-create-dash.mdx @@ -0,0 +1,26 @@ +--- +params: + - conditional? +--- + +import { Details, Render } from "~/components"; + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** and select **Create an internal zone**. +3. Give your internal zone a descriptive name. + +{ props.conditional === "get-started-detail" && ( +
+ +
+ ) +} + +4. Add DNS records to your internal zone using your preferred option: +- [Import](/dns/manage-dns-records/how-to/import-and-export/) a formatted BIND file. +- Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. +5. Repeat this process for each internal zone you wish to add. + +:::note +Creating multiple internal DNS records in batch is currently only supported via API. +::: \ No newline at end of file From aa561fb9931ec4075ccfbf13a81a2c166a043fbb Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 26 May 2025 16:43:29 +0100 Subject: [PATCH 08/18] Add reference zone dash steps and intro to get-started --- src/content/docs/dns/internal-dns/get-started.mdx | 11 +++++++++-- .../internal-zones/reference-zones.mdx | 2 +- .../partials/dns/internal-reference-zone-intro.mdx | 14 ++++++++++++++ 3 files changed, 24 insertions(+), 3 deletions(-) create mode 100644 src/content/partials/dns/internal-reference-zone-intro.mdx diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index cb463c3ebe40047..f1f56abd93a3658 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -54,13 +54,20 @@ Follow this guide to get started with Internal DNS. ### (Optional) Reference a zone from another zone + + -(Dash instructions) +1. Go to **Internal DNS** and select a zone. +2. Within the selected zone, go to **Reference zone**. +3. Select **Add reference zone**. +4. Find the zone you want to use as reference and choose **Select** in the respective row. -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/). +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 `--json`, specify the `internal_dns` object with the parameter `reference_zone_id`. 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 27481815c20ad3a..11d23c0cf5952db 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 @@ -7,7 +7,7 @@ sidebar: import { Example, Render, Tabs, TabItem } from "~/components"; -During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain. + :::note A wildcard record (`*.example.local`) in the matching internal zone will take precedence over an exact match in a referenced zone. diff --git a/src/content/partials/dns/internal-reference-zone-intro.mdx b/src/content/partials/dns/internal-reference-zone-intro.mdx new file mode 100644 index 000000000000000..71d7c7621b8fda4 --- /dev/null +++ b/src/content/partials/dns/internal-reference-zone-intro.mdx @@ -0,0 +1,14 @@ +--- +params: + - conditional? +--- + +During an [internal DNS query resolution](/dns/internal-dns/#architecture-overview), if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is referencing another internal zone. Successive references can be followed with a maximum of five references in a chain. + + +{ props.conditional === "get-started-link" && ( +

+ For details, refer to reference zones. +

+ ) +} \ No newline at end of file From 3ddc1ba6d3faa39c1f17130d79545bc7b71b50f7 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 26 May 2025 16:50:02 +0100 Subject: [PATCH 09/18] Create and apply partial for view-create-dash --- src/content/docs/dns/internal-dns/dns-views.mdx | 7 +------ src/content/docs/dns/internal-dns/get-started.mdx | 2 +- .../partials/dns/internal-dns-view-create-dash.mdx | 11 +++++++++++ 3 files changed, 13 insertions(+), 7 deletions(-) create mode 100644 src/content/partials/dns/internal-dns-view-create-dash.mdx diff --git a/src/content/docs/dns/internal-dns/dns-views.mdx b/src/content/docs/dns/internal-dns/dns-views.mdx index 8c9d4085c2ddaa4..6dd4b9e33d2759b 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -22,12 +22,7 @@ When setting up DNS views, observe the following conditions: -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. -2. Go to **Internal DNS** > **Views**. -3. Select **Create a view**. -4. Give your view a descriptive name. -5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view -6. Choose **Save** to confirm. + diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index f1f56abd93a3658..1ec3eb7ad7b258a 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -81,7 +81,7 @@ Since the resolver policy will require a [DNS view](/dns/internal-dns/dns-views/ -(Dash instructions) + diff --git a/src/content/partials/dns/internal-dns-view-create-dash.mdx b/src/content/partials/dns/internal-dns-view-create-dash.mdx new file mode 100644 index 000000000000000..d862677242e9ccb --- /dev/null +++ b/src/content/partials/dns/internal-dns-view-create-dash.mdx @@ -0,0 +1,11 @@ +--- +{} + +--- + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +2. Go to **Internal DNS** > **Views**. +3. Select **Create a view**. +4. Give your view a descriptive name. +5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view +6. Choose **Save** to confirm. \ No newline at end of file From 6aaaf90e8034a2be6569c8ffd0ce5536484734c5 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 26 May 2025 18:21:16 +0100 Subject: [PATCH 10/18] Overall review and add conditions to view creation partial --- src/content/docs/dns/internal-dns/get-started.mdx | 8 ++++++-- .../partials/dns/internal-dns-view-create-dash.mdx | 14 ++++++++++++-- .../partials/dns/internal-zone-create-dash.mdx | 2 +- .../partials/dns/internal-zones-conditions.mdx | 6 ++++-- 4 files changed, 23 insertions(+), 7 deletions(-) diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index 1ec3eb7ad7b258a..d2361cde8660cf3 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -81,7 +81,9 @@ Since the resolver policy will require a [DNS view](/dns/internal-dns/dns-views/ - + @@ -122,4 +124,6 @@ Use the rule settings object to define `resolve_dns_internally`, specifying `vie - `none`: Gateway DNS resolver returns the response as-is to the client. - `public_dns`: In case the response from the internal zone is REFUSED, NXDOMAIN, or a response with a CNAME type, Gateway DNS resolver sends the query to Cloudflare 1.1.1.1 public resolver and tries to resolve the query via public DNS. - \ No newline at end of file + + +Once you add the Gateway resolver policy, it will be listed in the respective internal view under **Resolver policies referencing this view**. \ No newline at end of file diff --git a/src/content/partials/dns/internal-dns-view-create-dash.mdx b/src/content/partials/dns/internal-dns-view-create-dash.mdx index d862677242e9ccb..0c43eb0f920623d 100644 --- a/src/content/partials/dns/internal-dns-view-create-dash.mdx +++ b/src/content/partials/dns/internal-dns-view-create-dash.mdx @@ -1,11 +1,21 @@ --- -{} - +params: + - conditional? --- +import { Details, Render } from "~/components"; + 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. 2. Go to **Internal DNS** > **Views**. 3. Select **Create a view**. 4. Give your view a descriptive name. + +{ props.conditional === "get-started-detail" && ( +
+ +
+ ) +} + 5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view 6. Choose **Save** to confirm. \ No newline at end of file diff --git a/src/content/partials/dns/internal-zone-create-dash.mdx b/src/content/partials/dns/internal-zone-create-dash.mdx index 8a5ab14f3b7370f..6069d5e9d5f6005 100644 --- a/src/content/partials/dns/internal-zone-create-dash.mdx +++ b/src/content/partials/dns/internal-zone-create-dash.mdx @@ -18,7 +18,7 @@ import { Details, Render } from "~/components"; 4. Add DNS records to your internal zone using your preferred option: - [Import](/dns/manage-dns-records/how-to/import-and-export/) a formatted BIND file. -- Select **Add a record** > **Create** under the selected record type and **Save record** after filling in the required fields. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. +- Select **Add a record** and choose **Create** under the record type you want to add. Refer to [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) for details. 5. Repeat this process for each internal zone you wish to add. :::note diff --git a/src/content/partials/dns/internal-zones-conditions.mdx b/src/content/partials/dns/internal-zones-conditions.mdx index 30e5dd0b6359ea7..df6451d558f38a8 100644 --- a/src/content/partials/dns/internal-zones-conditions.mdx +++ b/src/content/partials/dns/internal-zones-conditions.mdx @@ -5,6 +5,8 @@ - Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones. - An internal zone can have the same name as a public zone in the same account. -- Each internal zone can be linked to multiple [views](/dns/internal-dns/dns-views/). +- Each internal zone can be linked to multiple [views](/dns/internal-dns/dns-views/)[^20]. - There can be several internal zones with the same name in one account. However, two internal zones with the same name cannot be linked to the same view. -- Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`). \ No newline at end of file +- Internal zones are not subject to any top-level domain (TLD) restrictions. This means that an internal zone can be created if its TLD is not registered publicly (for example, `xyz.local`), if it is created on the TLD itself (`local`), or even if on the root (`.`). + +[^20]: Logical groupings of internal DNS zones that are referenced by Gateway resolver policies to define how a specific query should be resolved. \ No newline at end of file From 49b728dbed3941d4760a2518446529f95c0e5062 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 27 May 2025 09:51:20 +0100 Subject: [PATCH 11/18] Overall review and link to iDNS from docs landing page --- src/content/docs/dns/index.mdx | 2 ++ src/content/docs/dns/internal-dns/index.mdx | 2 +- .../dns/internal-dns/internal-zones/internal-dns-records.mdx | 2 +- .../docs/dns/internal-dns/internal-zones/reference-zones.mdx | 2 +- 4 files changed, 5 insertions(+), 3 deletions(-) diff --git a/src/content/docs/dns/index.mdx b/src/content/docs/dns/index.mdx index 2085a0a3bfdc9ab..4cefa142a4519e0 100644 --- a/src/content/docs/dns/index.mdx +++ b/src/content/docs/dns/index.mdx @@ -17,6 +17,8 @@ Leverage Cloudflare's global network to deliver excellent performance and reliab Cloudflare DNS is a fast, resilient and easy-to-manage authoritative DNS service. It delivers excellent performance and reliability to your domain while also protecting your business from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) and [route leaks and hijacking](https://www.cloudflare.com/learning/security/glossary/bgp-hijacking/). To know where to begin, refer to [Get started](/dns/get-started/). +Enterprise customers can also use Cloudflare DNS for their private network with [Intenal DNS (Beta)](/dns/internal-dns/) + *** ## Features diff --git a/src/content/docs/dns/internal-dns/index.mdx b/src/content/docs/dns/internal-dns/index.mdx index b88295c2a37b2d6..32b8f75af33013a 100644 --- a/src/content/docs/dns/internal-dns/index.mdx +++ b/src/content/docs/dns/internal-dns/index.mdx @@ -21,7 +21,7 @@ Simplify private network management with Cloudflare DNS for your internal resour -Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to the query context, such as query source IP. +Manage DNS records that should only be accessible within your private network. Internal DNS [zones](/dns/internal-dns/internal-zones/) and [views](/dns/internal-dns/dns-views/) pair up with [Gateway resolver policies](/cloudflare-one/policies/gateway/resolver-policies/) so that you can control how a DNS query should be responded to according to query context, such as query source IP. diff --git a/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx b/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx index a048db2f1722103..b9515e35254d38c 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx @@ -16,7 +16,7 @@ Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/ ## CNAME flattening in Internal DNS -With CNAME flattening, Cloudflare finds the final target content that a CNAME points to and then returns this content instead of a CNAME record. With Internal DNS, CNAME flattening is applied by default and cannot be turned off. +With [CNAME flattening](/dns/cname-flattening/), Cloudflare finds the final target content that a CNAME points to and then returns this content instead of a CNAME record. With Internal DNS, CNAME flattening is applied by default and cannot be turned off. Cloudflare will try to flatten the CNAME record considering both the specified [DNS view](/dns/internal-dns/dns-views/) and any existing [reference zones](/dns/internal-dns/internal-zones/reference-zones/). If the reference zone then has another CNAME, the record will again be considered from the perspective of the original view. 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 11d23c0cf5952db..ad396300f1424ba 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 @@ -10,7 +10,7 @@ import { Example, Render, Tabs, TabItem } from "~/components"; :::note -A wildcard record (`*.example.local`) in the matching internal zone will take precedence over an exact match in a referenced zone. +A wildcard record (`*.example.local`) in the matching internal zone will take precedence over an exact match in a reference zone. ::: ## Configuration conditions From 4364cd03220846478b15f5d362456fb603841466 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 28 May 2025 15:52:58 +0100 Subject: [PATCH 12/18] Specify reference at the bottom of internal zones and view is API-only --- src/content/docs/dns/internal-dns/dns-views.mdx | 2 +- src/content/docs/dns/internal-dns/internal-zones/setup.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 6dd4b9e33d2759b..407112be30421ba 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -52,7 +52,7 @@ Use the [Delete Internal DNS View](/api/resources/dns/subresources/settings/subr -## Other actions +## Other API actions - [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`) diff --git a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx index ff84eb18c642e6a..6884eb0ae444da4 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx @@ -28,7 +28,7 @@ When setting up internal zones, observe the following conditions: -## Other actions +## Other API actions The API endpoints to manage internal zones are the same as for managing public zones. The main difference is that the zone type must be set to `internal`. Refer to the API documentation below for details: From b0fd936abd31a77640d170dadb3f54fb9d6ef950 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 28 May 2025 16:06:54 +0100 Subject: [PATCH 13/18] Add Internal DNS to /products page --- src/content/products/internal-dns.yaml | 9 +++++++++ 1 file changed, 9 insertions(+) create mode 100644 src/content/products/internal-dns.yaml diff --git a/src/content/products/internal-dns.yaml b/src/content/products/internal-dns.yaml new file mode 100644 index 000000000000000..e4c6711a39d7d95 --- /dev/null +++ b/src/content/products/internal-dns.yaml @@ -0,0 +1,9 @@ +name: Internal DNS + +product: + title: Internal DNS + group: Application performance + url: /dns/internal-dns/ + +meta: + description: Use Cloudflare DNS for your internal resources. From cc353db65e94b6e10340d4766e3bbb5442e6ba98 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 4 Jun 2025 11:15:50 +0100 Subject: [PATCH 14/18] Remove 'descriptive' specification for zone name --- src/content/partials/dns/internal-zone-create-dash.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/partials/dns/internal-zone-create-dash.mdx b/src/content/partials/dns/internal-zone-create-dash.mdx index 6069d5e9d5f6005..76c4a463d6475c4 100644 --- a/src/content/partials/dns/internal-zone-create-dash.mdx +++ b/src/content/partials/dns/internal-zone-create-dash.mdx @@ -7,7 +7,7 @@ import { Details, Render } from "~/components"; 1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. 2. Go to **Internal DNS** and select **Create an internal zone**. -3. Give your internal zone a descriptive name. +3. Give your internal zone a name. { props.conditional === "get-started-detail" && (
From 5e036fb24d917baaf6bbb19aa8f12326bbb61b35 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 4 Jun 2025 12:05:20 +0100 Subject: [PATCH 15/18] Update get-started to match Gateway resolver UI text --- src/content/docs/dns/internal-dns/get-started.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index d2361cde8660cf3..4524e350b5a9ccd 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -109,7 +109,7 @@ Besides selecting an internal DNS view when setting up your resolver policies, y 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Resolver policies**. 2. Select **Add a policy** and enter a name and description. 3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors). -4. Select **Use DNS view**. In the dropdown, choose the view that queries matching the expression should be sent to. +4. Select **Use Internal DNS**. In the dropdown, choose the view that queries matching the expression should be sent to. 5. (Optional) Adjust the option to **fallback through public DNS** according to your use case. - Off: Gateway DNS resolver returns the response as-is to the client. - On: In case the response from the internal zone is REFUSED, NXDOMAIN, or a response with a CNAME type, Gateway DNS resolver sends the query to Cloudflare 1.1.1.1 public resolver and tries to resolve the query via public DNS. From 023b2090a566a02c107349da4684cff85ba824df Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 4 Jun 2025 12:19:02 +0100 Subject: [PATCH 16/18] Fix typo --- src/content/docs/dns/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/index.mdx b/src/content/docs/dns/index.mdx index 4cefa142a4519e0..68f2b37ab38cc04 100644 --- a/src/content/docs/dns/index.mdx +++ b/src/content/docs/dns/index.mdx @@ -17,7 +17,7 @@ Leverage Cloudflare's global network to deliver excellent performance and reliab Cloudflare DNS is a fast, resilient and easy-to-manage authoritative DNS service. It delivers excellent performance and reliability to your domain while also protecting your business from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) and [route leaks and hijacking](https://www.cloudflare.com/learning/security/glossary/bgp-hijacking/). To know where to begin, refer to [Get started](/dns/get-started/). -Enterprise customers can also use Cloudflare DNS for their private network with [Intenal DNS (Beta)](/dns/internal-dns/) +Enterprise customers can also use Cloudflare DNS for their private network with [Internal DNS (Beta)](/dns/internal-dns/) *** From ba9fd22a37f3d0edf13d72cd2d7565071184faf6 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro <62246989+RebeccaTamachiro@users.noreply.github.com> Date: Thu, 5 Jun 2025 14:14:55 +0100 Subject: [PATCH 17/18] Apply suggestions from code review Co-authored-by: Maddy <130055405+Maddy-Cloudflare@users.noreply.github.com> --- src/content/docs/dns/internal-dns/dns-views.mdx | 2 +- src/content/docs/dns/internal-dns/get-started.mdx | 2 +- .../docs/dns/internal-dns/internal-zones/reference-zones.mdx | 2 +- src/content/partials/dns/internal-dns-view-create-dash.mdx | 4 ++-- src/content/partials/dns/internal-zone-create-dash.mdx | 2 +- 5 files changed, 6 insertions(+), 6 deletions(-) diff --git a/src/content/docs/dns/internal-dns/dns-views.mdx b/src/content/docs/dns/internal-dns/dns-views.mdx index 407112be30421ba..904910797db40b6 100644 --- a/src/content/docs/dns/internal-dns/dns-views.mdx +++ b/src/content/docs/dns/internal-dns/dns-views.mdx @@ -39,7 +39,7 @@ It is also possible to delete a DNS view that is being referenced by a Gateway r -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. 2. Go to **Internal DNS** > **Views**. 3. Find the view you want to delete. 4. Select the three dots in the corresponding row and choose *Delete*. diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx index 4524e350b5a9ccd..d2e9b9b87df8da2 100644 --- a/src/content/docs/dns/internal-dns/get-started.mdx +++ b/src/content/docs/dns/internal-dns/get-started.mdx @@ -109,7 +109,7 @@ Besides selecting an internal DNS view when setting up your resolver policies, y 1. In [Zero Trust](https://one.dash.cloudflare.com/), go to **Gateway** > **Resolver policies**. 2. Select **Add a policy** and enter a name and description. 3. Create an expression for the traffic you wish to route. For guidance about selectors, operators, and values, refer to [Gateway](/cloudflare-one/policies/gateway/resolver-policies/#selectors). -4. Select **Use Internal DNS**. In the dropdown, choose the view that queries matching the expression should be sent to. +4. Select **Use Internal DNS**. Choose the view that queries matching the expression should be sent to. 5. (Optional) Adjust the option to **fallback through public DNS** according to your use case. - Off: Gateway DNS resolver returns the response as-is to the client. - On: In case the response from the internal zone is REFUSED, NXDOMAIN, or a response with a CNAME type, Gateway DNS resolver sends the query to Cloudflare 1.1.1.1 public resolver and tries to resolve the query via public DNS. 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 ad396300f1424ba..9a12336af2c5925 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 @@ -24,7 +24,7 @@ A wildcard record (`*.example.local`) in the matching internal zone will take pr -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. 2. Go to **Internal DNS** and select a zone. 3. Within the selected zone, go to **Reference zone**. 4. Select **Add reference zone**. If your zone already has a reference zone set up, you must first remove it. As explained in the [configuration conditions](#configuration-conditions), each internal zone can only reference one other zone at a time. diff --git a/src/content/partials/dns/internal-dns-view-create-dash.mdx b/src/content/partials/dns/internal-dns-view-create-dash.mdx index 0c43eb0f920623d..f81190342208de2 100644 --- a/src/content/partials/dns/internal-dns-view-create-dash.mdx +++ b/src/content/partials/dns/internal-dns-view-create-dash.mdx @@ -5,7 +5,7 @@ params: import { Details, Render } from "~/components"; -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. 2. Go to **Internal DNS** > **Views**. 3. Select **Create a view**. 4. Give your view a descriptive name. @@ -17,5 +17,5 @@ import { Details, Render } from "~/components"; ) } -5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view +5. Select **Manage zones** to add zones to your view. Select the internal zones that should be used to resolve queries sent by Gateway resolver to this view. 6. Choose **Save** to confirm. \ No newline at end of file diff --git a/src/content/partials/dns/internal-zone-create-dash.mdx b/src/content/partials/dns/internal-zone-create-dash.mdx index 76c4a463d6475c4..7e92cac6e1f3bde 100644 --- a/src/content/partials/dns/internal-zone-create-dash.mdx +++ b/src/content/partials/dns/internal-zone-create-dash.mdx @@ -5,7 +5,7 @@ params: import { Details, Render } from "~/components"; -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select an account. +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account. 2. Go to **Internal DNS** and select **Create an internal zone**. 3. Give your internal zone a name. From e60d3b56acc9f9946bc404ffecc28c502ba88640 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Thu, 5 Jun 2025 14:21:47 +0100 Subject: [PATCH 18/18] Add missing period and implement some page descriptions --- src/content/docs/dns/index.mdx | 2 +- src/content/docs/dns/internal-dns/internal-zones/index.mdx | 1 + .../dns/internal-dns/internal-zones/internal-dns-records.mdx | 1 + .../docs/dns/internal-dns/internal-zones/reference-zones.mdx | 1 + src/content/docs/dns/internal-dns/internal-zones/setup.mdx | 1 + 5 files changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/index.mdx b/src/content/docs/dns/index.mdx index 68f2b37ab38cc04..8155bf04aa2e602 100644 --- a/src/content/docs/dns/index.mdx +++ b/src/content/docs/dns/index.mdx @@ -17,7 +17,7 @@ Leverage Cloudflare's global network to deliver excellent performance and reliab Cloudflare DNS is a fast, resilient and easy-to-manage authoritative DNS service. It delivers excellent performance and reliability to your domain while also protecting your business from [DDoS attacks](https://www.cloudflare.com/learning/ddos/what-is-a-ddos-attack/) and [route leaks and hijacking](https://www.cloudflare.com/learning/security/glossary/bgp-hijacking/). To know where to begin, refer to [Get started](/dns/get-started/). -Enterprise customers can also use Cloudflare DNS for their private network with [Internal DNS (Beta)](/dns/internal-dns/) +Enterprise customers can also use Cloudflare DNS for their private network with [Internal DNS (Beta)](/dns/internal-dns/). *** diff --git a/src/content/docs/dns/internal-dns/internal-zones/index.mdx b/src/content/docs/dns/internal-dns/internal-zones/index.mdx index 3c37c6ff73d4c69..ad7e7ac2e2c0363 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/index.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/index.mdx @@ -1,6 +1,7 @@ --- pcx_content_type: concept title: Internal zones +description: Explore internal DNS zones in Cloudflare. These zones organize DNS records for resources accessible only within your private network, queried via Cloudflare Gateway. sidebar: order: 2 group: diff --git a/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx b/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx index b9515e35254d38c..775fc1e02d89835 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/internal-dns-records.mdx @@ -1,6 +1,7 @@ --- pcx_content_type: concept title: Manage internal DNS records +description: Manage internal DNS records in Cloudflare. Learn about supported DNS record types and CNAME flattening. sidebar: order: 4 label: Internal DNS records 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 9a12336af2c5925..f4705ece9329dac 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 @@ -1,6 +1,7 @@ --- pcx_content_type: how-to title: Reference zones +description: Learn about reference zones. Cloudflare Internal DNS allows zones to reference others for query resolution when no direct record is found. sidebar: order: 4 --- diff --git a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx index 6884eb0ae444da4..986767bf5a4cc88 100644 --- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx +++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx @@ -1,6 +1,7 @@ --- pcx_content_type: how-to title: Manage internal zones +description: Understand how to set up and manage internal DNS zones with Cloudflare. Explore configuration conditions, zone creation, and available API endpoints. sidebar: order: 2 ---