Skip to content

Commit e0b3b10

Browse files
Improve records examples and consolidate Flattening callouts
1 parent f6791ba commit e0b3b10

File tree

1 file changed

+12
-7
lines changed

1 file changed

+12
-7
lines changed

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

Lines changed: 12 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -72,23 +72,28 @@ Add a [`CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/) to Cl
7272

7373
To use Cloudflare DNS with AWS Amplify, refer to the [Amplify help content](https://docs.aws.amazon.com/amplify/latest/userguide/to-add-a-custom-domain-managed-by-a-third-party-dns-provider.html) and follow the instructions for **manual configuration**.
7474

75-
You will need at least two `CNAME` records:
75+
At Cloudflare, you will need at least two `CNAME` records:
7676

7777
- A <GlossaryTooltip term="proxy status">DNS-only</GlossaryTooltip> `CNAME` to validate your domain ownership, which should look like the following:
7878

7979
<Example>
80-
| Type | Name | Target | Proxy status | Flatten |
81-
| ------- | ----- | -------------------------------------------- | ------------ |---------|
82-
| `CNAME` | `<UNIQUE_STRING>.example.com` | `<UNIQUE_STRING>.mhbtsbpdnt.acm-validation.aws` | DNS only | False |
80+
| Type | Name | Target | Proxy status |
81+
| ------- | ----- | -------------------------------------------- | ------------ |
82+
| `CNAME` | `<UNIQUE_STRING>` | `<UNIQUE_STRING>.mhbtsbpdnt.acm-validation.aws` | DNS only |
8383
</Example>
8484

85-
:::caution
86-
<Render file="cname-flattening-callout" />
85+
:::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)
8787
:::
8888

89-
- One `CNAME` for the <GlossaryTooltip term="apex domain">apex domain</GlossaryTooltip> and/or for each of the subdomains that you want to proxy through Cloudflare.
89+
- 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.
9090

9191
<Example>
92+
93+
| Type | Name | Target |
94+
| ------- | ----- | -------------------------------------------- |
95+
| `CNAME` | `@` | `<AMPLIFY_HOSTNAME>.cloudfront.net` |
96+
9297
| Type | Name | Target |
9398
| ------- | ----- | -------------------------------------------- |
9499
| `CNAME` | `blog` | `<AMPLIFY_HOSTNAME>.cloudfront.net` |

0 commit comments

Comments
 (0)