Skip to content

Commit e7eb4cf

Browse files
Remove CNAME flattening desc to be added on a separate PR
1 parent 938dbf6 commit e7eb4cf

File tree

1 file changed

+1
-12
lines changed
  • src/content/docs/dns/internal-dns/internal-zones

1 file changed

+1
-12
lines changed

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

Lines changed: 1 addition & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -27,15 +27,4 @@ Internal zones can contain the same [DNS record types](/dns/manage-dns-records/r
2727

2828
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.
2929

30-
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.
31-
32-
### CNAME flattening
33-
34-
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.
35-
36-
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:
37-
38-
1. The CNAME record is returned to Gateway resolver as-is.
39-
2. Gateway resolver will process the returned record, depending on the **Fallback through public DNS** configuration:
40-
- 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/)).
41-
- Off: Gateway will return the response as-is to the client.
30+
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.

0 commit comments

Comments
 (0)