From 296acffd50a934a4d5bd497341776ad2e7765a82 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 24 Sep 2024 18:05:11 +0100 Subject: [PATCH 01/13] Create conversions folder and add .mdx files of new guides --- .../conversions/convert-full-to-secondary.mdx | 54 +++++++++++++++ .../conversions/convert-secondary-to-full.mdx | 41 ++++++++++++ .../convert-secondary-to-partial.mdx | 67 +++++++++++++++++++ .../dns/zone-setups/conversions/index.mdx | 15 +++++ src/content/docs/dns/zone-setups/removal.mdx | 2 +- 5 files changed, 178 insertions(+), 1 deletion(-) create mode 100644 src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx create mode 100644 src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx create mode 100644 src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx create mode 100644 src/content/docs/dns/zone-setups/conversions/index.mdx diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx new file mode 100644 index 000000000000000..eb501dcffefa7c9 --- /dev/null +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -0,0 +1,54 @@ +--- +title: Convert full setup to secondary setup +pcx_content_type: tutorial +sidebar: + order: 1 + label: Full to secondary +--- + +import { Tabs, TabItem, Render, GlossaryTooltip } from "~/components"; + +If you initially configured a [full setup](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/). + +Follow the steps below to achieve this conversion. + +## 1. Prepare DNS records + +1. [Export a zone file](/dns/manage-dns-records/how-to/import-and-export/#export-records). +2. Import the zone file into your new primary DNS provider. +3. At your Cloudflare zone, use the [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoint to enable [secondary DNS overrides](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/). Set the value for `secondary_overrides` to `true`. + + :::note + Enabling secondary DNS overrides is necessary in case you have DNS records that you wish to keep proxied. + ::: + +## 2. Prepare the zone transfers + +1. (Optional) Make adjustments to DNSSEC according to your option for [DNSSEC with secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/). +2. (Optional) Create a Transaction Signature (TSIG). + + + + + + + + + + + + + +3. Create peer server. + + + +## 3. Convert the zone and initiate zone transfers + +1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `secondary`, to convert the zone type. The existing records will remain in place. +2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +3. Link the peer server you created in the previous steps and select **Save**. +4. On **DNS** > **Settings**, select **Initiate zone transfer**. +5. Confirm the DNS records are transferring as expected. +6. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) and take note of your new **Cloudflare Nameservers**. +7. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/) to include the `secondary.cloudflare.com` nameservers. \ No newline at end of file diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx new file mode 100644 index 000000000000000..75c97dcfd838813 --- /dev/null +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -0,0 +1,41 @@ +--- +title: Convert secondary setup to full setup +pcx_content_type: tutorial +sidebar: + order: 5 + label: Secondary to full + +--- + +If you initially set up [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a full setup. + +Follow the steps below to achieve this conversion. + +## 1. Stop transferring the zone + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. +2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +3. Unlink the peer and select **Save**. + +## 2. Prepare for the conversion + +1. Plan for [DNSSEC settings](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/). If you were previously using [Pre-signed DNSSEC](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/#set-up-pre-signed-dnssec), consider disabling DNSSEC before starting the conversion. +2. Make sure the [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) of your DNS records are consistently set: + + - If you have [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/), confirm each record has the appropriate setting (**Proxied** or **DNS only**). + - If [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/) is disabled, make sure all of your DNS records are listed as **DNS only**. + +3. (Optional) For consistency, apply SOA record overrides according to your needs. Once Cloudflare automatically generates an SOA record for your zone on full setup, the field overrides will be considered. + +## 3. Convert your zone + +1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `full`, to convert the zone type. Existing DNS records will not be affected. +2. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) and take note of your new **Cloudflare Nameservers**. +3. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/). Replace the nameservers ending in `secondary.cloudflare.com` by the ones ending in `ns.cloudflare.com`. + + :::note + If Cloudflare will be your only primary DNS provider, remove any other nameservers as well. + ::: + +4. Delete the previous SOA record to make sure Cloudflare generates a new one. +5. (Optional) If Cloudflare was previously not signing your records and you wish to use DNSSEC, follow the steps to [Enable DNSSEC](/dns/dnssec/#enable-dnssec). \ No newline at end of file diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx new file mode 100644 index 000000000000000..7b703b037d901cb --- /dev/null +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -0,0 +1,67 @@ +--- +title: Convert secondary setup to partial setup +pcx_content_type: tutorial +sidebar: + order: 5 + label: Secondary to partial + +--- + + +import { GlossaryTooltip, Details } from "~/components"; + +If you initially setup [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a partial setup. + +Follow the steps below to achieve this conversion. + +## 1. Stop transferring the zone + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. +2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +3. Unlink the peer and select **Save**. + +## 2. Configure your authoritative DNS provider + +1. (Optional) If you are also migrating to a new authoritative DNS provider, export a zone file from the previous provider and import into the new one. +2. At your authoritative DNS provider, 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: + + ```txt + www.example.com CNAME www.example.com.cdn.cloudflare.net + ``` +
+ +3. At your authoritative DNS provider, 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`. + +## 3. Convert your Cloudflare zone + +1. Back at your Cloudflare zone, confirm that you have all the [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for the hostnames you pointed to `{your-hostname}.cdn.cloudflare.net` in the previous step. +2. Go to the [Overview page](https://dash.cloudflare.com/?to=/:account/:zone) and select **Convert to CNAME DNS Setup**. +3. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider. + +
+ + A verification record for `sub.example.com` might be: + + | Type | Name | Content | + | ---- | ------------------------------- | ------------------- | + | TXT | `cloudflare-verify.sub.example.com` | 966215192-518620144 | + + 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.sub.example.com.sub.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. + +
+ + :::note + The verification record must remain in place for as long as you want your partial setup to be active on Cloudflare. + ::: + +## 4. Update nameservers + +1. At your domain registrar (or parent zone), [update the nameservers](/dns/nameservers/update-nameservers/). + + In a partial (CNAME) setup, only the nameservers of your external DNS provider should be listed. Remove any `secondary.cloudflare.com` nameservers if you used to have them. \ No newline at end of file diff --git a/src/content/docs/dns/zone-setups/conversions/index.mdx b/src/content/docs/dns/zone-setups/conversions/index.mdx new file mode 100644 index 000000000000000..ffa8fa025f1cdf0 --- /dev/null +++ b/src/content/docs/dns/zone-setups/conversions/index.mdx @@ -0,0 +1,15 @@ +--- +pcx_content_type: navigation +title: Zone setup conversions +sidebar: + order: 10 + group: + hideIndex: true + label: Zone conversions +--- + +import { DirectoryListing } from "~/components"; + +You can perform the following zone setup conversions: + + \ No newline at end of file diff --git a/src/content/docs/dns/zone-setups/removal.mdx b/src/content/docs/dns/zone-setups/removal.mdx index 9713aafed6e8eac..1a59d15d670d8eb 100644 --- a/src/content/docs/dns/zone-setups/removal.mdx +++ b/src/content/docs/dns/zone-setups/removal.mdx @@ -2,7 +2,7 @@ title: Zone removal pcx_content_type: concept sidebar: - order: 8 + order: 12 --- From a4d8670e2ba4a7d4350f388a037b5f3bc4cfa8bd Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 25 Sep 2024 13:58:04 +0100 Subject: [PATCH 02/13] Process comments from gdoc review for full-to-secondary --- .../dns/zone-setups/conversions/convert-full-to-secondary.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx index eb501dcffefa7c9..52775f17d17369b 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -24,7 +24,7 @@ Follow the steps below to achieve this conversion. ## 2. Prepare the zone transfers -1. (Optional) Make adjustments to DNSSEC according to your option for [DNSSEC with secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/). +1. Make adjustments to DNSSEC according to your option for [DNSSEC with secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/). 2. (Optional) Create a Transaction Signature (TSIG). @@ -39,7 +39,7 @@ Follow the steps below to achieve this conversion. -3. Create peer server. +3. Create a peer server. From 6e0373be9371e425a6283335550729a54d78496d Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Wed, 25 Sep 2024 14:19:34 +0100 Subject: [PATCH 03/13] Process comments from gdoc review for secondary-to-full --- .../dns/zone-setups/conversions/convert-secondary-to-full.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index 75c97dcfd838813..d12852c335ce8ee 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -25,7 +25,7 @@ Follow the steps below to achieve this conversion. - If you have [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/), confirm each record has the appropriate setting (**Proxied** or **DNS only**). - If [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/) is disabled, make sure all of your DNS records are listed as **DNS only**. -3. (Optional) For consistency, apply SOA record overrides according to your needs. Once Cloudflare automatically generates an SOA record for your zone on full setup, the field overrides will be considered. +3. (Optional) For consistency, use the [Update DNS Settings](/api/operations/dns-settings-for-a-zone-update-dns-settings) endpoint to specify SOA record fields according to your needs. Once Cloudflare automatically generates an SOA record for your zone on full setup, the field overrides will be considered. ## 3. Convert your zone From 090f859f69f7c403d49955d9a53db08287abb88f Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 13:43:54 +0100 Subject: [PATCH 04/13] Add note about read-only state after unlinking peers --- .../dns/zone-setups/conversions/convert-secondary-to-full.mdx | 4 +++- .../zone-setups/conversions/convert-secondary-to-partial.mdx | 2 ++ 2 files changed, 5 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index d12852c335ce8ee..cbaae0698a39c40 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -17,10 +17,12 @@ Follow the steps below to achieve this conversion. 2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. 3. Unlink the peer and select **Save**. +At this point, your zone will be read-only, meaning you cannot make any edits. + ## 2. Prepare for the conversion 1. Plan for [DNSSEC settings](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/). If you were previously using [Pre-signed DNSSEC](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/dnssec-for-secondary/#set-up-pre-signed-dnssec), consider disabling DNSSEC before starting the conversion. -2. Make sure the [proxy status](/dns/manage-dns-records/reference/proxied-dns-records/) of your DNS records are consistently set: +2. Make sure the [proxy statuses](/dns/manage-dns-records/reference/proxied-dns-records/) of your DNS records are consistently set: - If you have [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/), confirm each record has the appropriate setting (**Proxied** or **DNS only**). - If [Secondary DNS override](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/proxy-traffic/) is disabled, make sure all of your DNS records are listed as **DNS only**. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index 7b703b037d901cb..f92ed6b3ea08c98 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -20,6 +20,8 @@ Follow the steps below to achieve this conversion. 2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. 3. Unlink the peer and select **Save**. +At this point, your zone will be read-only, meaning you cannot make any edits. + ## 2. Configure your authoritative DNS provider 1. (Optional) If you are also migrating to a new authoritative DNS provider, export a zone file from the previous provider and import into the new one. From 5357ae4d0c47fba1ab643202b0669201166b8d91 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 13:48:06 +0100 Subject: [PATCH 05/13] Move repeated text into partial and apply it --- .../conversions/convert-secondary-to-full.mdx | 8 +++----- .../conversions/convert-secondary-to-partial.mdx | 8 ++------ .../partials/dns/secondary-conversion-unlink.mdx | 10 ++++++++++ 3 files changed, 15 insertions(+), 11 deletions(-) create mode 100644 src/content/partials/dns/secondary-conversion-unlink.mdx diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index cbaae0698a39c40..95af4b47ac69b6c 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -7,17 +7,15 @@ sidebar: --- +import { Render } from "~/components"; + If you initially set up [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a full setup. Follow the steps below to achieve this conversion. ## 1. Stop transferring the zone -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. -2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. -3. Unlink the peer and select **Save**. - -At this point, your zone will be read-only, meaning you cannot make any edits. + ## 2. Prepare for the conversion diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index f92ed6b3ea08c98..bcbea837bfcd30e 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -8,7 +8,7 @@ sidebar: --- -import { GlossaryTooltip, Details } from "~/components"; +import { GlossaryTooltip, Details, Render } from "~/components"; If you initially setup [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a partial setup. @@ -16,11 +16,7 @@ Follow the steps below to achieve this conversion. ## 1. Stop transferring the zone -1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. -2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. -3. Unlink the peer and select **Save**. - -At this point, your zone will be read-only, meaning you cannot make any edits. + ## 2. Configure your authoritative DNS provider diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx new file mode 100644 index 000000000000000..e73e4ce4d99ad93 --- /dev/null +++ b/src/content/partials/dns/secondary-conversion-unlink.mdx @@ -0,0 +1,10 @@ +--- +{} + +--- + +1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/login) and select your account and zone. +2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. +3. Unlink the peer and select **Save**. + +At this point, your zone will be read-only, meaning you cannot make any edits. \ No newline at end of file From 492015a657b8129c39ef9bb1684f694ef7fe25f2 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 14:15:36 +0100 Subject: [PATCH 06/13] Review convert-secondary-to-partial --- .../conversions/convert-secondary-to-partial.mdx | 10 ++++------ .../partials/dns/secondary-conversion-unlink.mdx | 2 +- 2 files changed, 5 insertions(+), 7 deletions(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index bcbea837bfcd30e..a2bb7c0d3593c6f 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -10,7 +10,7 @@ sidebar: import { GlossaryTooltip, Details, Render } from "~/components"; -If you initially setup [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a partial setup. +If you initially set up [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a partial setup. Follow the steps below to achieve this conversion. @@ -36,8 +36,8 @@ Follow the steps below to achieve this conversion. ## 3. Convert your Cloudflare zone -1. Back at your Cloudflare zone, confirm that you have all the [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for the hostnames you pointed to `{your-hostname}.cdn.cloudflare.net` in the previous step. -2. Go to the [Overview page](https://dash.cloudflare.com/?to=/:account/:zone) and select **Convert to CNAME DNS Setup**. +1. Back at your Cloudflare zone, confirm that you have all the `A`, `AAAA`, or `CNAME` [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for the hostnames you pointed to `{your-hostname}.cdn.cloudflare.net` in the previous step. You can also delete any DNS records that have a different type, as they will no longer resolve once you convert your zone to a partial setup. +2. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `partial`, to convert the zone type. Existing DNS records will not be affected. 3. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider.
@@ -60,6 +60,4 @@ Follow the steps below to achieve this conversion. ## 4. Update nameservers -1. At your domain registrar (or parent zone), [update the nameservers](/dns/nameservers/update-nameservers/). - - In a partial (CNAME) setup, only the nameservers of your external DNS provider should be listed. Remove any `secondary.cloudflare.com` nameservers if you used to have them. \ No newline at end of file +1. At your domain registrar (or parent zone), [update the nameservers](/dns/nameservers/update-nameservers/). In a partial (CNAME) setup, only the nameservers of your external DNS provider should be listed. Remove any `secondary.cloudflare.com` nameservers if you used to have them. \ No newline at end of file diff --git a/src/content/partials/dns/secondary-conversion-unlink.mdx b/src/content/partials/dns/secondary-conversion-unlink.mdx index e73e4ce4d99ad93..2fdc6a359863025 100644 --- a/src/content/partials/dns/secondary-conversion-unlink.mdx +++ b/src/content/partials/dns/secondary-conversion-unlink.mdx @@ -7,4 +7,4 @@ 2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. 3. Unlink the peer and select **Save**. -At this point, your zone will be read-only, meaning you cannot make any edits. \ No newline at end of file +At this point, your zone will be read-only. \ No newline at end of file From c72ba632b04269c14d81af69715e385d032c49d8 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 14:31:37 +0100 Subject: [PATCH 07/13] Move partial docs to conversions folder, re-order, and add redirects --- public/_redirects | 2 ++ .../conversions/convert-full-to-secondary.mdx | 2 +- .../convert-partial-to-full.mdx | 9 +++------ .../convert-partial-to-secondary.mdx | 8 +++----- .../conversions/convert-secondary-to-full.mdx | 2 +- .../conversions/convert-secondary-to-partial.mdx | 2 +- 6 files changed, 11 insertions(+), 14 deletions(-) rename src/content/docs/dns/zone-setups/{partial-setup => conversions}/convert-partial-to-full.mdx (96%) rename src/content/docs/dns/zone-setups/{partial-setup => conversions}/convert-partial-to-secondary.mdx (98%) diff --git a/public/_redirects b/public/_redirects index b5d24ef97e1db8a..962bcf65f13f424 100644 --- a/public/_redirects +++ b/public/_redirects @@ -317,6 +317,8 @@ /dns/manage-dns-records/how-to/dns-load-balancing/ /dns/manage-dns-records/how-to/round-robin-dns/ 301 /dns/manage-dns-records/how-to/create-root-domain/ /dns/manage-dns-records/how-to/create-zone-apex/ 301 /dns/reference/troubleshooting/ /dns/reference/recommended-third-party-tools/ 301 +/dns/zone-setups/partial-setup/convert-partial-to-full/ /dns/zone-setups/conversions/convert-partial-to-full/ 301 +/dns/zone-setups/partial-setup/convert-partial-to-secondary/ /dns/zone-setups/conversions/convert-partial-to-secondary/ 301 /dns/zone-setups/troubleshooting/dns-probe-finished-nxdomain/ /dns/troubleshooting/dns-probe-finished-nxdomain/ 301 /dns/zone-setups/troubleshooting/nameservers/ /dns/zone-setups/full-setup/troubleshooting/ 301 /support/dns/ /dns/ 301 diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx index 52775f17d17369b..c6f3947ea46ea86 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -2,7 +2,7 @@ title: Convert full setup to secondary setup pcx_content_type: tutorial sidebar: - order: 1 + order: 2 label: Full to secondary --- diff --git a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx similarity index 96% rename from src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-full.mdx rename to src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx index 521db75bbbbe2b8..52796a37a6cdca2 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx @@ -1,12 +1,9 @@ --- -title: Convert to full setup +title: Convert partial setup to full setup pcx_content_type: tutorial sidebar: - order: 3 -head: - - tag: title - content: Convert partial setup to full setup - + order: 4 + label: Partial to full --- If you initially set up a partial domain on Cloudflare, you can later migrate it to a [full setup](/dns/zone-setups/full-setup/). diff --git a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx similarity index 98% rename from src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx rename to src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx index 057f006b21f0df8..6d880cd6ab092b7 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/convert-partial-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx @@ -1,11 +1,9 @@ --- -title: Convert to secondary setup +title: Convert partial setup to secondary setup pcx_content_type: tutorial sidebar: - order: 4 -head: - - tag: title - content: Convert partial setup to secondary setup + order: 5 + label: Partial to secondary --- import { Details, Render, TabItem, Tabs } from "~/components"; diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index 95af4b47ac69b6c..47af9b551a95641 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -2,7 +2,7 @@ title: Convert secondary setup to full setup pcx_content_type: tutorial sidebar: - order: 5 + order: 7 label: Secondary to full --- diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index a2bb7c0d3593c6f..d0ed2c1c8d37bc0 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -2,7 +2,7 @@ title: Convert secondary setup to partial setup pcx_content_type: tutorial sidebar: - order: 5 + order: 8 label: Secondary to partial --- From 3c15ce5447a3e2d8504d64b5ab73ffe935a1da81 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 14:40:17 +0100 Subject: [PATCH 08/13] For completeness, add external_link page pointing to partial-setup/setup --- .../zone-setups/conversions/convert-full-to-partial.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) create mode 100644 src/content/docs/dns/zone-setups/conversions/convert-full-to-partial.mdx diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-partial.mdx new file mode 100644 index 000000000000000..1213d10f2742199 --- /dev/null +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-partial.mdx @@ -0,0 +1,8 @@ +--- +pcx_content_type: navigation +title: Convert full setup to partial setup +external_link: /dns/zone-setups/partial-setup/setup/ +sidebar: + order: 1 + label: Full to partial +--- \ No newline at end of file From f18834b135c5da54e95fc58d63ed9b2ef29b2d41 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 15:16:32 +0100 Subject: [PATCH 09/13] Fix broken link and list convert-partial-to-secondary as well --- src/content/docs/dns/zone-setups/partial-setup/index.mdx | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/zone-setups/partial-setup/index.mdx b/src/content/docs/dns/zone-setups/partial-setup/index.mdx index 0e8011f4364f3f5..a5bd605da69f071 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/index.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/index.mdx @@ -15,7 +15,8 @@ Once you are on a partial setup, the actual resolution of your records to Cloudf ## How to * [Set up a partial domain](/dns/zone-setups/partial-setup/setup/) -* [Convert a partial domain to a full domain](/dns/zone-setups/partial-setup/convert-partial-to-full/) +* [Convert a partial setup to a full setup](/dns/zone-setups/conversions/convert-partial-to-full/) +* [Convert a partial setup to a secondary setup](/dns/zone-setups/partial-setup/convert-partial-to-secondary/) ## Availability From dad7597d03f2c8e74aa236d20ea661a6d114afd6 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Tue, 1 Oct 2024 15:46:15 +0100 Subject: [PATCH 10/13] Add correct link for convert-partial-to-secondary --- src/content/docs/dns/zone-setups/partial-setup/index.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/docs/dns/zone-setups/partial-setup/index.mdx b/src/content/docs/dns/zone-setups/partial-setup/index.mdx index a5bd605da69f071..aed3068315db030 100644 --- a/src/content/docs/dns/zone-setups/partial-setup/index.mdx +++ b/src/content/docs/dns/zone-setups/partial-setup/index.mdx @@ -16,7 +16,7 @@ Once you are on a partial setup, the actual resolution of your records to Cloudf * [Set up a partial domain](/dns/zone-setups/partial-setup/setup/) * [Convert a partial setup to a full setup](/dns/zone-setups/conversions/convert-partial-to-full/) -* [Convert a partial setup to a secondary setup](/dns/zone-setups/partial-setup/convert-partial-to-secondary/) +* [Convert a partial setup to a secondary setup](/dns/zone-setups/conversions/convert-partial-to-secondary/) ## Availability From fdc7f247329d8fa54f30aada601d1eb88ade968c Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 14 Oct 2024 17:09:52 +0100 Subject: [PATCH 11/13] Add call out regarding subdomain setup as per PM suggestion --- .../conversions/convert-full-to-secondary.mdx | 2 ++ .../conversions/convert-partial-to-full.mdx | 4 ++++ .../conversions/convert-partial-to-secondary.mdx | 2 ++ .../conversions/convert-secondary-to-full.mdx | 2 ++ .../conversions/convert-secondary-to-partial.mdx | 2 ++ .../dns/conversion-subdomain-setup-callout.mdx | 10 ++++++++++ 6 files changed, 22 insertions(+) create mode 100644 src/content/partials/dns/conversion-subdomain-setup-callout.mdx diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx index c6f3947ea46ea86..d2f0530e68664f3 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -10,6 +10,8 @@ import { Tabs, TabItem, Render, GlossaryTooltip } from "~/components"; If you initially configured a [full setup](/dns/zone-setups/full-setup/), you can later convert your zone to use [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/). + + Follow the steps below to achieve this conversion. ## 1. Prepare DNS records diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx index 37dd42eb664d88e..e709c0e7831ef69 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-full.mdx @@ -6,8 +6,12 @@ sidebar: label: Partial to full --- +import { Render } from "~/components"; + If you initially set up a partial domain on Cloudflare, you can later migrate it to a [full setup](/dns/zone-setups/full-setup/). + + ## 1. Prepare Cloudflare SSL/TLS In the Cloudflare dashboard, either order an [advanced certificate](/ssl/edge-certificates/advanced-certificate-manager/manage-certificates/) or [upload a custom SSL certificate](/ssl/edge-certificates/custom-certificates/uploading/) for your website or application. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx index 6d880cd6ab092b7..8fbcba8381610d7 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-partial-to-secondary.mdx @@ -10,6 +10,8 @@ import { Details, Render, TabItem, Tabs } from "~/components"; If you initially set up a [partial zone](/dns/zone-setups/partial-setup/) on Cloudflare, you can later convert it to use a [secondary setup](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/). + + This page will guide you through this conversion using [export and import](/dns/manage-dns-records/how-to/import-and-export/) and API calls. ## Before you begin diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index 47af9b551a95641..414f400b9562ed5 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -11,6 +11,8 @@ import { Render } from "~/components"; If you initially set up [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a full setup. + + Follow the steps below to achieve this conversion. ## 1. Stop transferring the zone diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index d0ed2c1c8d37bc0..a157515a632dbfb 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -12,6 +12,8 @@ import { GlossaryTooltip, Details, Render } from "~/components"; If you initially set up [incoming zone transfers (Cloudflare as secondary)](/dns/zone-setups/zone-transfers/cloudflare-as-secondary/setup/), you can later convert your zone to use a partial setup. + + Follow the steps below to achieve this conversion. ## 1. Stop transferring the zone diff --git a/src/content/partials/dns/conversion-subdomain-setup-callout.mdx b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx new file mode 100644 index 000000000000000..2d6ccf3c0e1d1b4 --- /dev/null +++ b/src/content/partials/dns/conversion-subdomain-setup-callout.mdx @@ -0,0 +1,10 @@ +--- +{} + +--- + +:::caution[Subdomain setup] +If you also use subdomain setup[^1], consider the [available combinations](/dns/zone-setups/subdomain-setup/setup/#available-setups) and whether your zone conversion could have any implications. +::: + +[^1]: Meaning you have one or more subdomains (`sub.example.com`) added to Cloudflare as their own zone, separate from your apex domain (`example.com`). \ No newline at end of file From 50c8829a19c6ac736d379a0a719e3f60944a420f Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro Date: Mon, 14 Oct 2024 18:21:21 +0100 Subject: [PATCH 12/13] Explicitly state what NS updates could be needed as per PM suggestion --- .../zone-setups/conversions/convert-secondary-to-partial.mdx | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index a157515a632dbfb..18fca33812e563d 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -62,4 +62,7 @@ Follow the steps below to achieve this conversion. ## 4. Update nameservers -1. At your domain registrar (or parent zone), [update the nameservers](/dns/nameservers/update-nameservers/). In a partial (CNAME) setup, only the nameservers of your external DNS provider should be listed. Remove any `secondary.cloudflare.com` nameservers if you used to have them. \ No newline at end of file +At your domain registrar (or parent zone), [update the nameservers](/dns/nameservers/update-nameservers/). In a partial (CNAME) setup, only the nameservers of your external DNS provider should be listed. + + - Remove any `secondary.cloudflare.com` nameservers if you used to have them. + - If you are also migrating to a new authoritative DNS provider, add your new nameservers. \ No newline at end of file From 101d0d9768260935d8d0540fb92650685797e435 Mon Sep 17 00:00:00 2001 From: Rebecca Tamachiro <62246989+RebeccaTamachiro@users.noreply.github.com> Date: Tue, 15 Oct 2024 14:13:17 +0100 Subject: [PATCH 13/13] Apply suggestions from code review Co-authored-by: Jun Lee --- .../dns/zone-setups/conversions/convert-full-to-secondary.mdx | 2 +- .../dns/zone-setups/conversions/convert-secondary-to-full.mdx | 2 +- .../zone-setups/conversions/convert-secondary-to-partial.mdx | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx index d2f0530e68664f3..925e7f3715a1497 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-full-to-secondary.mdx @@ -47,7 +47,7 @@ Follow the steps below to achieve this conversion. ## 3. Convert the zone and initiate zone transfers -1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `secondary`, to convert the zone type. The existing records will remain in place. +1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `secondary` to convert the zone type. The existing records will remain in place. 2. Go to **DNS** > **Settings** > **DNS Zone Transfers** and select **Manage linked peers**. 3. Link the peer server you created in the previous steps and select **Save**. 4. On **DNS** > **Settings**, select **Initiate zone transfer**. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx index 414f400b9562ed5..e231b0405b7f1e1 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-full.mdx @@ -31,7 +31,7 @@ Follow the steps below to achieve this conversion. ## 3. Convert your zone -1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `full`, to convert the zone type. Existing DNS records will not be affected. +1. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `full` to convert the zone type. Existing DNS records will not be affected. 2. Go to [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records) and take note of your new **Cloudflare Nameservers**. 3. At your domain registrar (or parent zone), [update your nameservers](/dns/nameservers/update-nameservers/). Replace the nameservers ending in `secondary.cloudflare.com` by the ones ending in `ns.cloudflare.com`. diff --git a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx index 18fca33812e563d..ac6f16d8e26396e 100644 --- a/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx +++ b/src/content/docs/dns/zone-setups/conversions/convert-secondary-to-partial.mdx @@ -22,7 +22,7 @@ Follow the steps below to achieve this conversion. ## 2. Configure your authoritative DNS provider -1. (Optional) If you are also migrating to a new authoritative DNS provider, export a zone file from the previous provider and import into the new one. +1. (Optional) If you are also migrating to a new authoritative DNS provider, export a zone file from the previous provider and import it into the new one. 2. At your authoritative DNS provider, create `CNAME` records pointing to `{your-hostname}.cdn.cloudflare.net` for every hostname you wish to proxy through Cloudflare.
@@ -39,7 +39,7 @@ Follow the steps below to achieve this conversion. ## 3. Convert your Cloudflare zone 1. Back at your Cloudflare zone, confirm that you have all the `A`, `AAAA`, or `CNAME` [DNS records](/dns/manage-dns-records/how-to/create-dns-records/) needed for the hostnames you pointed to `{your-hostname}.cdn.cloudflare.net` in the previous step. You can also delete any DNS records that have a different type, as they will no longer resolve once you convert your zone to a partial setup. -2. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `partial`, to convert the zone type. Existing DNS records will not be affected. +2. Use the [Edit Zone endpoint](/api/operations/zones-0-patch) with `type` set to `partial` to convert the zone type. Existing DNS records will not be affected. 3. On [**DNS** > **Records**](https://dash.cloudflare.com/?to=/:account/:zone/dns/records), get the **Verification TXT Record** and add it at your authoritative DNS provider.