Skip to content

Commit becd9e6

Browse files
[DNS] Call out supported records in partial setup (#18770)
* Explicitly reference record types that users are able to create via UI * Point to API if other DNS record types are needed * Make formatting more consistent within index.mdx * Apply suggestion from code review Co-authored-by: Max Phillips <[email protected]> --------- Co-authored-by: Max Phillips <[email protected]>
1 parent 1e1987c commit becd9e6

File tree

3 files changed

+13
-6
lines changed

3 files changed

+13
-6
lines changed

src/content/docs/dns/zone-setups/partial-setup/index.mdx

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,13 +10,14 @@ import { FeatureTable, Render } from "~/components"
1010

1111
<Render file="partial-setup-definition" />
1212

13-
Once you are on a partial setup, the actual resolution of your records to Cloudflare depends on `CNAME` records [added at your authoritative DNS provider](/dns/zone-setups/partial-setup/setup/#3-add-dns-records). Check your authoritative DNS provider to know which records are pointing to `{your-hostname}.cdn.cloudflare.net`.
13+
Once you are on a partial setup, the actual resolution of your records to Cloudflare depends on CNAME records [added at your authoritative DNS provider](/dns/zone-setups/partial-setup/setup/#3-add-dns-records). Check your authoritative DNS provider to know which records are pointing to `{your-hostname}.cdn.cloudflare.net`.
1414

1515
## How to
1616

1717
* [Set up a partial domain](/dns/zone-setups/partial-setup/setup/)
1818
* [Convert a partial setup to a full setup](/dns/zone-setups/conversions/convert-partial-to-full/)
1919
* [Convert a partial setup to a secondary setup](/dns/zone-setups/conversions/convert-partial-to-secondary/)
20+
* [Create DNS records of other types](/dns/zone-setups/partial-setup/setup/#other-record-types)
2021

2122
## Availability
2223

@@ -30,7 +31,7 @@ With a partial zone, Cloudflare resolves [DNS records differently](/dns/zone-set
3031

3132
### CNAME flattening
3233

33-
A partial (`CNAME`) setup requires the proxied hostname to be pointed to Cloudflare via a `CNAME` record. Since [`CNAME` records are not allowed on the zone apex](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4) (`example.com`), you can only proxy your zone apex to Cloudflare if your authoritative DNS provider supports [`CNAME` Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/).
34+
A partial (CNAME) setup requires the proxied hostname to be pointed to Cloudflare via a CNAME record. Since [CNAME records are not allowed on the zone apex](https://datatracker.ietf.org/doc/html/rfc1912#section-2.4) (`example.com`), you can only proxy your zone apex to Cloudflare if your authoritative DNS provider supports [CNAME Flattening](https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/).
3435

3536
If your authoritative DNS provider does not support CNAME Flattening, redirect its traffic — for example, with an `.htaccess` file — to a subdomain proxied to Cloudflare. Alternatively, you can use [static IPs or BYOIPs](/fundamentals/concepts/cloudflare-ip-addresses/#customize-cloudflare-ip-addresses).
3637

src/content/docs/dns/zone-setups/partial-setup/setup.mdx

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ A partial setup is only available to customers on a Business or Enterprise plan.
3838
1. On the **Overview** page, select **Convert to CNAME DNS Setup**.
3939
2. Select **Convert** to confirm.
4040
3. Save the information from the **Verification TXT Record**. If you lose the information, you can also access it by going to **DNS** > **Records** > **Verification TXT Record**.
41-
4. Make sure that you have all the DNS records for subdomains that you want to proxy through Cloudflare.
41+
4. Make sure that you have all the DNS records (A, AAAA, or CNAME) for subdomains that you want to proxy through Cloudflare.
4242
</Steps>
4343

4444
## 2. Verify ownership for your domain
@@ -81,4 +81,10 @@ If your organization has multiple Cloudflare accounts, also consider using zone
8181
2. Remove any previously existing `A`, `AAAA`, or `CNAME` records referencing the hostnames you want to proxy through Cloudflare. For these hostnames, leave only the records pointing to `{your-hostname}.cdn.cloudflare.net`.
8282

8383
2. Repeat this process for each subdomain that should be proxied to Cloudflare.
84-
</Steps>
84+
</Steps>
85+
86+
---
87+
88+
## Other record types
89+
90+
If you are preparing a conversion from partial to full setup, or if you have a more specific use case, you can use the [Create DNS Record](/api/operations/dns-records-for-a-zone-create-dns-record) API endpoint to create DNS records of any supported type.

src/content/partials/dns/partial-setup-definition.mdx

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,6 @@
55

66
import { GlossaryTooltip } from "~/components"
77

8-
A partial (`CNAME`) setup allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
8+
A partial (CNAME) setup allows you to use [Cloudflare's reverse proxy](/fundamentals/concepts/how-cloudflare-works/) while maintaining your primary and authoritative DNS provider.
99

10-
Use this option to <GlossaryTooltip term="proxy status">proxy</GlossaryTooltip> only individual subdomains through Cloudflare's global network when you cannot change your authoritative DNS provider.
10+
Use this option to <GlossaryTooltip term="proxy status">proxy</GlossaryTooltip> only individual subdomains through Cloudflare when you cannot change your authoritative DNS provider. You will be able to create A, AAAA, and CNAME records, which are the DNS record types that can be [proxied](/dns/manage-dns-records/reference/proxied-dns-records/).

0 commit comments

Comments
 (0)