Skip to content

Commit a65c64a

Browse files
Add example where other records are not returned if orange CNAME
1 parent 5f5de06 commit a65c64a

File tree

1 file changed

+25
-2
lines changed

1 file changed

+25
-2
lines changed

src/content/docs/dns/manage-dns-records/reference/dns-record-types.mdx

Lines changed: 25 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,7 @@ sidebar:
66

77
---
88

9-
import { Details, Render, APIRequest, GlossaryTooltip } from "~/components"
9+
import { Details, Render, APIRequest, GlossaryTooltip, Example } from "~/components"
1010

1111
This page provides information about some of the different types of DNS records that you can manage on Cloudflare. For guidance on how to add, edit, or delete DNS records, refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/).
1212

@@ -111,7 +111,30 @@ These records include the following fields:
111111

112112
Observe the following aspects, especially before changing a CNAME record from <GlossaryTooltip term="proxy status" link="/dns/proxy-status/">proxied</GlossaryTooltip> to DNS-only or vice versa:
113113

114-
- If a hostname is meant to proxy traffic, you can use CNAME records to point to other CNAME records (`www.example2.com` --> `www.example1.com` --> `www.example.com`), but the final record must point to a hostname with a valid IP address (and therefore a valid A or AAAA record).
114+
- If a hostname is meant to proxy traffic, you can use CNAME records to point to other CNAME records (`www.example2.com` --> `www.example1.com` --> `www.example.com`), but the final record must point to a hostname with a valid IP address (and therefore a valid A or AAAA record). Also, queries for other record types on the same name are not supported.
115+
116+
<Details header="Example">
117+
118+
<Example>
119+
DNS management for **example.com**:
120+
121+
| Type | Name | Content | Proxy status |
122+
| -------- | ------- | ----------------------- | ------------- |
123+
| CNAME | abc | `target.external.test` | DNS Only |
124+
</Example>
125+
126+
<Example>
127+
DNS management for **external.test**:
128+
129+
| Type | Name | Content |
130+
| ------- | --------- | --------------------- |
131+
| A | target | `192.0.2.1` |
132+
| TXT | target | `"some TXT content"` |
133+
</Example>
134+
135+
In this example, a query for TXT in `abc.example.com` will **not** return the TXT content in the target zone.
136+
137+
</Details>
115138

116139
- Cloudflare uses a process called CNAME flattening to deliver better performance. This process supports a few features and can interact with [different setups that depend on CNAME records](/dns/cname-flattening/#aspects-to-keep-in-mind). Refer to the [CNAME flattening section](/dns/cname-flattening/) to learn more about this.
117140

0 commit comments

Comments
 (0)