Re-org and further detail reference zones conditions

Author: RebeccaTamachiro

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

@@ -23,7 +23,7 @@ Cloudflare will try to flatten the CNAME record considering both the specified [
 <Details header="Example">
 
 - Query for `abc.example.local` with view ID 111.
-- Zone 600 references zone 700, which does not belong to any view.
+- Zone 600 references zone 700, which is not linked to any view.
 
 ```mermaid
 flowchart LR

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

@@ -7,7 +7,18 @@ sidebar:
 
 import { Example, Render } from "~/components";
 
-<Render file="reference-zone-intro" />
+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.
+:::
+
+## Configuration conditions
+
+- Each internal zone can only reference one other zone.
+- The same zone can be referenced by multiple internal zones.
+- Public zones cannot be used as reference zones.
+- Reference zones do not have to be linked to the same [DNS view](/dns/internal-dns/dns-views/) as the zone referencing them. They may also not be linked to any view at all.
 
 ## Set up
 

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

@@ -7,7 +7,7 @@ sidebar:
 
 import { Example, Render } from "~/components";
 
-Refer to the following sections to learn how to manage your internal DNS zones.
+Refer to the following sections to learn how to manage your [internal DNS zones](/dns/internal-dns/internal-zones/).
 
 ## Configuration conditions