|
9 | 9 |
|
10 | 10 | --- |
11 | 11 |
|
12 | | -import { Details, Render } from "~/components" |
| 12 | +import { Details, Render, GlossaryTooltip, Steps } from "~/components"; |
13 | 13 |
|
14 | 14 | <Render file="partial-setup-definition" /> |
15 | 15 |
|
16 | 16 | :::note |
17 | | - |
18 | | - |
19 | 17 | A partial setup is only available to customers on a Business or Enterprise plan. |
20 | | - |
21 | | - |
22 | 18 | ::: |
23 | 19 |
|
24 | 20 | *** |
25 | 21 |
|
26 | | -## Add your domain to Cloudflare |
27 | | - |
28 | | - |
29 | | -1. Create a Cloudflare account and [add your domain](/fundamentals/setup/manage-domains/add-site/). |
30 | | - |
31 | | -2. For your **Plan**, choose **Business** or **Enterprise**. |
| 22 | +## Before you begin |
32 | 23 |
|
33 | | -3. Continue through the onboarding steps, ignoring the instructions to change your nameservers. |
| 24 | +<Steps> |
| 25 | +1. Create a Cloudflare account and add your domain. |
| 26 | +2. Choose **Business** or **Enterprise** as your plan. |
| 27 | +3. If you are onboarding a new domain to Cloudflare, ignore the instructions to change your nameservers. |
| 28 | +4. (Recommended) Plan for SSL/TLS certificates: |
34 | 29 |
|
35 | | -4. On the **Overview** page, select **Convert to CNAME DNS Setup**. |
| 30 | + 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. |
36 | 31 |
|
37 | | -5. Select **Convert** to confirm. |
| 32 | + 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). |
| 33 | +</Steps> |
38 | 34 |
|
39 | | -6. 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**. |
| 35 | +## 1. Convert your zone and review DNS records |
40 | 36 |
|
| 37 | +<Steps> |
| 38 | +1. On the **Overview** page, select **Convert to CNAME DNS Setup**. |
| 39 | +2. Select **Convert** to confirm. |
| 40 | +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. |
| 42 | +</Steps> |
41 | 43 |
|
42 | | -## Verify ownership for your domain |
43 | | - |
44 | | - |
45 | | -Once you [add your domain to Cloudflare](#add-your-domain-to-cloudflare), 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. |
| 44 | +## 2. Verify ownership for your domain |
46 | 45 |
|
| 46 | +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. |
47 | 47 |
|
48 | 48 | <Details header="Example verification record"> |
49 | | - |
50 | 49 | A verification record for `example.com` might be: |
51 | 50 |
|
52 | 51 | | Type | Name | Content | |
53 | 52 | | ---- | ------------------------------- | ------------------- | |
54 | 53 | | TXT | `cloudflare-verify.example.com` | 966215192-518620144 | |
55 | | - |
56 | | - |
57 | 54 | </Details> |
58 | 55 |
|
59 | 56 | :::note |
60 | | - |
61 | | - |
62 | 57 | 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`. |
63 | 58 |
|
64 | 59 | 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.<YOUR DOMAIN>` and validate if it is working. |
65 | | - |
66 | | - |
67 | 60 | ::: |
68 | 61 |
|
69 | 62 | That record must remain in place for as long as your domain is active on the partial setup on Cloudflare. |
70 | 63 |
|
| 64 | +## 3. Add DNS records |
71 | 65 |
|
72 | | -## Optional - Provision an SSL certificate |
73 | | - |
74 | | - |
75 | | -To provision a Universal SSL certificate through Cloudflare, follow [these instructions](/ssl/edge-certificates/universal-ssl/enable-universal-ssl/#partial-dns-setup). |
76 | | - |
77 | | -If your domain is already live with a partial (CNAME) setup — with Cloudflare or another DNS provider — you cannot use a TXT record for [Domain Control Validation](/ssl/edge-certificates/changing-dcv-method/methods/txt/). That domain's TXT record needs to be reserved for forwarding traffic to Cloudflare. |
78 | | - |
79 | | - |
80 | | -## Add DNS records |
81 | | - |
82 | | - |
83 | | -1. In Cloudflare, [add an `A`, `AAAA`, or `CNAME` record](/dns/manage-dns-records/how-to/create-dns-records/). |
84 | | -2. At your authoritative DNS provider: |
85 | | - |
86 | | - 1. Remove any existing `A`, `AAAA`, or `CNAME` records on the hostname you want to proxy to Cloudflare. |
87 | | - |
88 | | - 2. Add a `CNAME` record for `{your-hostname}.cdn.cloudflare.net`. |
89 | | - |
90 | | - <details> |
91 | | - <summary> |
92 | | - Example CNAME record at authoritative DNS provider |
93 | | - </summary> |
94 | | - |
95 | | - The `CNAME` record for `www.example.com` would be: |
| 66 | +<Steps> |
| 67 | +1. At your authoritative DNS provider: |
| 68 | + 1. Create `CNAME` records pointing to `{your-hostname}.cdn.cloudflare.net` for every hostname you wish to proxy through Cloudflare. |
96 | 69 |
|
97 | | - ```txt |
98 | | - www.example.com CNAME www.example.com.cdn.cloudflare.net |
99 | | - ``` |
| 70 | + <Details header="Example CNAME record at authoritative DNS provider"> |
100 | 71 |
|
101 | | - </details> |
| 72 | + The `CNAME` record for `www.example.com` would be: |
102 | 73 |
|
103 | | - 3. Repeat this process for each subdomain proxied to Cloudflare. |
| 74 | + ```txt |
| 75 | + www.example.com CNAME www.example.com.cdn.cloudflare.net |
| 76 | + ``` |
| 77 | + </Details> |
104 | 78 |
|
| 79 | + 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`. |
105 | 80 |
|
| 81 | +2. Repeat this process for each subdomain that should be proxied to Cloudflare. |
| 82 | +</Steps> |
0 commit comments