Create dedicated pages to reference zones and internal records

Author: RebeccaTamachiro

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/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"/>

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

@@ -76,7 +76,7 @@ flowchart LR
 				end
 ```
 
-Internal DNS zones contain the <GlossaryTooltip term="DNS record" link="/dns/internal-dns/internal-zones/#internal-dns-records">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 <GlossaryTooltip term="DNS record" link="/dns/internal-dns/internal-zones/internal-dns-records/">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/).
 
 <Example>
 

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

@@ -7,35 +7,14 @@ sidebar:
     label: Internal zones
 ---
 
-import { Example, Render } from "~/components";
+import { Example, Render, DirectoryListing } from "~/components";
 
-Internal DNS zones are groupings of internal DNS records. While [public DNS records](/dns/manage-dns-records/) contain information about resources that you want to make available to the public Internet, [internal DNS records](#internal-dns-records) allow you to manage resources that should only be available within your private network.
+Internal DNS zones are groupings of internal DNS records. While [public DNS records](/dns/manage-dns-records/) contain information about resources that you want to make available to the public Internet, [internal DNS records](/dns/internal-dns/internal-zones/internal-dns-records/) allow you to manage resources that should only be available within your private network.
 
 Refer to [Manage internal zones](/dns/internal-dns/internal-zones/setup/) for a full list of configuration conditions and step-by-step instructions.
 
 Internal DNS zones do not get assigned Cloudflare nameservers and can only be queried via [Cloudflare Gateway](/cloudflare-one/policies/gateway/resolver-policies/) when linked to a [DNS view](/dns/internal-dns/dns-views/). The Gateway configuration must exist within the same Cloudflare account where the internal zone exists.
 
-## Reference zones
+## Resources
 
-<Render file="reference-zone-intro" />
-
-Refer to [Set up reference zones](/dns/internal-dns/internal-zones/reference-zones/) for step-by-step instructions.
-
-## Internal DNS records
-
-Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
-
-You can manage internal DNS records in the same way as you would manage public DNS records, with the difference that [proxy status](/dns/proxy-status/) does not apply to internal DNS records.
-
-Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) or to the [API documentation](/api/resources/dns/subresources/records/) for further guidance.
-
-### CNAME flattening
-
-With CNAME flattening, Cloudflare finds the IP address that a CNAME points to and then returns the final IP address instead of a CNAME record. With Internal DNS, this behavior is applied by default and cannot be turned off.
-
-Cloudflare will try to flatten the CNAME record within the same [DNS view](/dns/internal-dns/dns-views/). If that is not possible, the following will happen:
-
-1. The CNAME record is returned to Gateway resolver as-is.
-2. Gateway resolver will process the returned record, depending on the **Fallback through public DNS** configuration:
-    - On: Gateway will try to resolve the query by sending it to Cloudflare's public DNS resolver ([1.1.1.1](/1.1.1.1/)).
-    - Off: Gateway will return the response as-is to the client.
+<DirectoryListing />

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

@@ -0,0 +1,24 @@
+---
+pcx_content_type: concept
+title: Manage internal DNS records
+sidebar:
+  order: 4
+  label: Internal DNS records
+---
+
+Internal zones can contain the same [DNS record types](/dns/manage-dns-records/reference/dns-record-types/) that Cloudflare supports for public zones.
+
+You can manage internal DNS records in the same way as you would manage public DNS records, with the difference that [proxy status](/dns/proxy-status/) does not apply to internal DNS records.
+
+Refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/) or to the [API documentation](/api/resources/dns/subresources/records/) for further guidance.
+
+### CNAME flattening
+
+With CNAME flattening, Cloudflare finds the IP address that a CNAME points to and then returns the final IP address instead of a CNAME record. With Internal DNS, this behavior is applied by default and cannot be turned off.
+
+Cloudflare will try to flatten the CNAME record within the same [DNS view](/dns/internal-dns/dns-views/). If that is not possible, the following will happen:
+
+1. The CNAME record is returned to Gateway resolver as-is.
+2. Gateway resolver will process the returned record, depending on the **Fallback through public DNS** configuration:
+    - On: Gateway will try to resolve the query by sending it to Cloudflare's public DNS resolver ([1.1.1.1](/1.1.1.1/)).
+    - Off: Gateway will return the response as-is to the client.

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

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: how-to
-title: Set up reference zones
+title: Reference zones
 sidebar:
   order: 4
 ---
@@ -9,7 +9,7 @@ import { Example, Render } from "~/components";
 
 <Render file="reference-zone-intro" />
 
-## Steps
+## 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`.