diff --git a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx index 886ab2ad0b41f71..9149deb0ee2de07 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/setup.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/setup.mdx @@ -6,7 +6,6 @@ sidebar: head: - tag: title content: Set up a partial (CNAME) zone - --- import { Details, Render, GlossaryTooltip, Steps } from "~/components"; @@ -17,28 +16,32 @@ import { Details, Render, GlossaryTooltip, Steps } from "~/components"; A partial setup is only available to customers on a Business or Enterprise plan. ::: -*** +--- ## Before you begin + 1. Create a Cloudflare account and add your domain. 2. Choose **Business** or **Enterprise** as your plan. 3. If you are onboarding a new domain to Cloudflare, ignore the instructions to change your nameservers. 4. (Recommended) Plan for SSL/TLS certificates: - If you are only using [Universal SSL](/ssl/edge-certificates/universal-ssl/) prior to converting your zone, a certificate will be provisioned for your subdomains only after each of the respective DNS records ([step 3](#3-add-dns-records) below) are [proxied](/dns/manage-dns-records/reference/proxied-dns-records/). Refer to [Enable Universal SSL](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup) for details. + If you are only using [Universal SSL](/ssl/edge-certificates/universal-ssl/) prior to converting your zone, a certificate will be provisioned for your subdomains only after each of the respective DNS records ([step 3](#3-add-dns-records) below) are [proxied](/dns/manage-dns-records/reference/proxied-dns-records/). Refer to [Enable Universal SSL](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup) for details. + + If your domain is sensitive to downtime, instead of using Universal SSL, consider using an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) with [delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/#setup). - If your domain is sensitive to downtime, instead of using Universal SSL, consider using an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/) with [delegated DCV](/ssl/edge-certificates/changing-dcv-method/methods/delegated-dcv/#setup). ## 1. Convert your zone and review DNS records + 1. On the **Overview** page, select **Convert to CNAME DNS Setup**. 2. Select **Convert** to confirm. 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**. 4. Make sure that you have all the DNS records (A, AAAA, or CNAME) for subdomains that you want to proxy through Cloudflare. + ## 2. Verify ownership for your domain @@ -46,17 +49,21 @@ A partial setup is only available to customers on a Business or Enterprise plan. Add the **Verification TXT Record** at your authoritative DNS provider. Cloudflare will verify the TXT record and send a confirmation email. This can take up to a few hours.
+ A verification record for `example.com` might be: | Type | Name | Content | | ---- | ------------------------------- | ------------------- | | TXT | `cloudflare-verify.example.com` | 966215192-518620144 | +
:::note + If your authoritative DNS provider automatically appends DNS record `name` fields with your domain, make sure to only insert `cloudflare-verify` as the record name. Otherwise, it may result in an incorrect record name, such as `cloudflare-verify.example.com.example.com`. -After creating the record, you can use this [Dig Web Interface link](https://digwebinterface.com/?type=TXT\&ns=auth\&nameservers=) to search (`dig`) for `cloudflare-verify.` and validate if it is working. +After creating the record, you can use this [Dig Web Interface link](https://digwebinterface.com/?type=TXT&ns=auth&nameservers=) to search (`dig`) for `cloudflare-verify.` and validate if it is working. + ::: That record must remain in place for as long as your domain is active on the partial setup on Cloudflare. @@ -66,25 +73,29 @@ If your organization has multiple Cloudflare accounts, also consider using zone ## 3. Add DNS records + 1. At your authoritative DNS provider: + 1. Create `CNAME` records pointing to `{your-hostname}.cdn.cloudflare.net` for every hostname you wish to proxy through Cloudflare. -
+
+ + The `CNAME` record for `www.example.com` would be: - The `CNAME` record for `www.example.com` would be: + ```txt + www.example.com CNAME www.example.com.cdn.cloudflare.net + ``` - ```txt - www.example.com CNAME www.example.com.cdn.cloudflare.net - ``` -
+
- 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`. + 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`. 2. Repeat this process for each subdomain that should be proxied to Cloudflare. + --- ## Other record types -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. \ No newline at end of file +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/resources/dns/subresources/records/methods/create/) API endpoint to create DNS records of any supported type.