Skip to content

Commit e3b5ccc

Browse files
Apply suggestion from code review
Co-authored-by: Jun Lee <[email protected]>
1 parent e0b3b10 commit e3b5ccc

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

src/content/docs/dns/manage-dns-records/reference/vendor-specific-records.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ At Cloudflare, you will need at least two `CNAME` records:
8383
</Example>
8484

8585
:::caution[CNAME flattening]
86-
If your Cloudflare zone is on a paid plan, also make sure that the **Flatten** option turned off for the validation `CNAME` record, and that you zone is **not** using [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records)
86+
If your Cloudflare zone is on a paid plan, also make sure that the **Flatten** option turned off for the validation `CNAME` record, and that you zone is **not** using [CNAME flattening for all CNAME records](/dns/cname-flattening/set-up-cname-flattening/#for-all-cname-records).
8787
:::
8888

8989
- One `CNAME` for the <GlossaryTooltip term="apex domain">apex domain</GlossaryTooltip> (`example.com`) and/or for each of the subdomains (`blog.example.com`) that you want to manage on Cloudflare. For details refer to [Manage DNS records](/dns/manage-dns-records/how-to/create-dns-records/). These records can be proxied.

0 commit comments

Comments
 (0)