Descride CNAME flattening behavior with reference zones and view

Author: RebeccaTamachiro

src/content/docs/dns/cname-flattening/index.mdx

@@ -20,6 +20,10 @@ With CNAME flattening, Cloudflare finds the IP address that a CNAME points to. T
 
 For more details on the steps involved in CNAME flattening, review the [CNAME flattening diagram](/dns/cname-flattening/cname-flattening-diagram/) and refer to the [Cloudflare blog post](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/).
 
+:::note
+For information about CNAME flattening in [Internal DNS](/dns/internal-dns/), refer to [internal DNS records](/dns/internal-dns/internal-zones/internal-dns-records/).
+:::
+
 ## Aspects to keep in mind
 
 * CNAME flattening happens by default in some cases. Refer to [Setup](/dns/cname-flattening/set-up-cname-flattening/) for details.

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

@@ -12,11 +12,13 @@ You can manage internal DNS records in the same way as you would manage public D
 
 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
+## 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:
+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.
+
+If it is not possible to flatten the CNAME record, 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: