diff --git a/src/content/docs/dns/cname-flattening/index.mdx b/src/content/docs/dns/cname-flattening/index.mdx
index dcdd96e576dce45..024337b483121f7 100644
--- a/src/content/docs/dns/cname-flattening/index.mdx
+++ b/src/content/docs/dns/cname-flattening/index.mdx
@@ -6,16 +6,12 @@ sidebar:
label: About
---
-import { Render } from "~/components"
+import { Render, GlossaryTooltip } from "~/components"
-CNAME flattening speeds up CNAME resolution and allows you to use a CNAME record at your root/apex domain (`example.com`).
+CNAME flattening speeds up CNAME resolution and allows you to use a CNAME record at your zone apex (`example.com`).
:::note
-
-
This functionality is also what allows you to use a [root custom domain](/pages/configuration/custom-domains/) with a Cloudflare Pages site.
-
-
:::
## How it works
diff --git a/src/content/docs/dns/internal-dns/get-started.mdx b/src/content/docs/dns/internal-dns/get-started.mdx
index b0a15f2359949da..9113e9ab1e86f44 100644
--- a/src/content/docs/dns/internal-dns/get-started.mdx
+++ b/src/content/docs/dns/internal-dns/get-started.mdx
@@ -41,16 +41,9 @@ Although there are some steps that can be achieved on the dashboard, currently t
## 1. Set up your internal DNS zone
-1. Use the [Create Zone](/api/resources/zones/) endpoint to create an [internal zone](/dns/internal-dns/internal-zones/). Specify your account ID and set the `type` to `internal`.
-
-
-
-
-
-2. Add DNS records to your internal zone using your preferred option:
-- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
-- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
-3. Repeat this process for each internal zone you wish to add.
+
### (Optional) Reference a zone from another zone
diff --git a/src/content/docs/dns/internal-dns/index.mdx b/src/content/docs/dns/internal-dns/index.mdx
index 3969a0ec6face30..14348e33e0b50d5 100644
--- a/src/content/docs/dns/internal-dns/index.mdx
+++ b/src/content/docs/dns/internal-dns/index.mdx
@@ -76,7 +76,7 @@ flowchart LR
end
```
-Internal DNS zones contain the DNS records GlossaryTooltip> that should be used to resolve an internal DNS query. Also, if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is [referencing another internal zone](/dns/internal-dns/internal-zones/#reference-zones).
+Internal DNS zones contain the DNS records GlossaryTooltip> that should be used to resolve an internal DNS query. Also, if no internal record is found within a matching internal zone, Cloudflare will check if the matching internal zone is [referencing another internal zone](/dns/internal-dns/internal-zones/#reference-zones).
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 5f4dfb4589219f3..04b0f1f95bbe182 100644
--- a/src/content/docs/dns/internal-dns/internal-zones/index.mdx
+++ b/src/content/docs/dns/internal-dns/internal-zones/index.mdx
@@ -17,9 +17,7 @@ Internal DNS zones do not get assigned Cloudflare nameservers and can only be qu
## Reference zones
-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.
-
-Each internal zone can only reference one other zone, but the same zone can be referenced by multiple internal zones. Public zones cannot be used as reference zones.
+
Refer to [Set up reference zones](/dns/internal-dns/internal-zones/reference-zones/) for step-by-step instructions.
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 0d0bee5d88639ca..f95374c11d3c3bf 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,9 +7,7 @@ sidebar:
import { Example, Render } 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.
-
-Each internal zone can only reference one other zone, but the same zone can be referenced by multiple internal zones. Public zones cannot be used as reference zones.
+
## Steps
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 9e7b29bba27631a..14d35e8716f5095 100644
--- a/src/content/docs/dns/internal-dns/internal-zones/setup.mdx
+++ b/src/content/docs/dns/internal-dns/internal-zones/setup.mdx
@@ -17,14 +17,7 @@ When setting up internal zones, observe the following conditions:
## Create an internal zone
-1. Use the [Create Zone](/api/resources/zones/) endpoint to create an internal zone. Specify your account ID and set the `type` to `internal`.
-2. Add DNS records to your internal zone using your preferred option:
-- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
-- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
-3. Repeat this process for each internal zone you wish to add.
-
-Since the resolver policy configuration will require a DNS view, you must link the internal zones to at least one view to be able to use them when routing requests to Internal DNS. For a full procedure overview, refer to [get started](/dns/internal-dns/get-started/).
-
+
## Other actions
diff --git a/src/content/glossary/dns.yaml b/src/content/glossary/dns.yaml
index c1e134dc8ffb4d4..593179167b174d3 100644
--- a/src/content/glossary/dns.yaml
+++ b/src/content/glossary/dns.yaml
@@ -27,7 +27,7 @@ entries:
- term: DNS record
general_definition: |-
- DNS records are instructions that live in authoritative DNS servers and provide information about a domain including what IP address is associated with that domain and how to handle requests for that domain.
+ DNS records are instructions that live in authoritative DNS servers and provide information about a domain, including what IP address is associated with that domain and how to handle requests for that domain.
- term: DNS server
general_definition: |-
@@ -79,3 +79,7 @@ entries:
When a [DNS record is proxied](/dns/proxy-status/), requests are processed according to your configurations, and Cloudflare can optimize, cache, and protect your domain. Refer to [How Cloudflare works](/fundamentals/concepts/how-cloudflare-works/) for details.
associated_products:
- Fundamentals
+
+ - term: zone apex
+ general_definition: |-
+ zone apex refers to the domain or subdomain on which the control of DNS records starts.
diff --git a/src/content/partials/dns/internal-zone-create.mdx b/src/content/partials/dns/internal-zone-create.mdx
new file mode 100644
index 000000000000000..a46c3c8a59f9827
--- /dev/null
+++ b/src/content/partials/dns/internal-zone-create.mdx
@@ -0,0 +1,20 @@
+---
+params:
+ - conditional?
+---
+
+import { Details, Render } from "~/components";
+
+1. Use the [Create Zone](/api/resources/zones/) endpoint to create an [internal zone](/dns/internal-dns/internal-zones/). Specify your account ID and set the `type` to `internal`.
+
+{ props.conditional === "get-started-detail" && (
+
+
+
+ )
+}
+
+2. Add DNS records to your internal zone using your preferred option:
+- [Import](/api/resources/dns/subresources/records/methods/import/) a formatted BIND file. Refer to the [DNS records how-to](/dns/manage-dns-records/how-to/import-and-export/) for guidance.
+- Use other API endpoints, such as [`/batch`](/api/resources/dns/subresources/records/methods/batch/), to manage DNS records. Refer to [Batch record changes](/dns/manage-dns-records/how-to/batch-record-changes/#use-the-api) for details.
+3. Repeat this process for each internal zone you wish to add.
\ No newline at end of file
diff --git a/src/content/partials/dns/reference-zone-intro.mdx b/src/content/partials/dns/reference-zone-intro.mdx
new file mode 100644
index 000000000000000..3e255f6a447513e
--- /dev/null
+++ b/src/content/partials/dns/reference-zone-intro.mdx
@@ -0,0 +1,12 @@
+---
+{}
+
+---
+
+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 in the matching internal zone will take precedence over an exact match in a referenced zone.
+:::
+
+Each internal zone can only reference one other zone, but the same zone can be referenced by multiple internal zones. Public zones cannot be used as reference zones.
\ No newline at end of file