Skip to content

Commit 8bc5858

Browse files
[DNS, Registrar] Clarify DNSSEC disablement when transferring a domain (#22610)
* Expand disable DNSSEC section within before-you-begin * Remove dupe step to unlock and link DNSSEC in #next-steps * Text touchup
1 parent 60259a9 commit 8bc5858

File tree

4 files changed

+24
-4
lines changed

4 files changed

+24
-4
lines changed

src/content/docs/registrar/get-started/transfer-domain-to-cloudflare.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ Transferring your domain to Cloudflare tells your registry that a different regi
1212

1313
Transferring a domain to a new registrar informs the registry that they should instead trust that new registrar to modify information. The process requires some action steps at your new and previous registrar. Each registrar handles transfers a bit differently, but in general, they follow a pattern based on rules set by ICANN, the organization responsible for regulating domain registration.
1414

15-
This section contains generic instructions on how to transfer your domain to Cloudflare from most registrars.
15+
This page contains generic instructions on how to transfer your domain to Cloudflare from most registrars.
1616

1717
***
1818

src/content/glossary/cache.yaml

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -68,6 +68,7 @@ entries:
6868
the duration for which a cached copy of a resource is considered valid before it needs to be refreshed or revalidated.
6969
associated_products:
7070
- Magic WAN
71+
- DNS
7172

7273
- term: cache lock
7374
general_definition: |-

src/content/partials/registrar/before-you-begin.mdx

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,21 +3,32 @@
33

44
---
55

6-
import { Render } from "~/components"
6+
import { Render, Details, GlossaryTooltip } from "~/components"
77

88
## Before transferring a domain to Cloudflare
99

1010
* Create [a Cloudflare account](/fundamentals/setup/account/create-account/).
1111
* [Add the domain](/fundamentals/setup/manage-domains/add-site/) you are transferring to your Cloudflare account.
1212
* [Review your DNS records](/dns/zone-setups/full-setup/setup/#review-dns-records) in the Cloudflare dashboard.
13+
* If needed, plan for [DNSSEC disablement](#disable-dnssec).
1314
* [Change your DNS nameservers](/dns/zone-setups/full-setup/) to Cloudflare.
1415
* If initiating multiple transfers, notify your financial institution to prevent them from flagging these charges as fraudulent.
1516
* Renew your domain if it is within 15 days of expiration.
16-
* Unlock your domain at your current registrar.
1717
* Do not make any changes to the Registrant contact information. Updating the Registrant contact may result in your current registrar locking the domain for 60 days.
1818
* Make sure your account has a valid credit card on file.
1919
* If you are transferring a `.us` domain, refer to the [Additional requirements for .US domains](/registrar/top-level-domains/us-domains/) before proceeding.
2020

2121
### Disable DNSSEC
2222

23-
<Render file="disable_dnssec" product="dns" />
23+
If you are onboarding an existing domain to Cloudflare, make sure DNSSEC **is disabled** at your registrar. Otherwise, your domain will experience connectivity errors when you change your nameservers.
24+
25+
1. Take note of the <GlossaryTooltip term="time-to-live (TTL)">TTL</GlossaryTooltip> value for the DS record at your current registrar.
26+
2. Remove DS records at your current registrar.
27+
<Render file="dnssec-providers" product="dns" />
28+
3. Wait at least the time corresponding to the DS record TTL. It is usually 24 hours, but refer to the value you got in step 1.
29+
4. Follow the steps to [transfer your domain](/registrar/get-started/transfer-domain-to-cloudflare/#set-up-a-domain-transfer) to Cloudflare Registrar.
30+
5. [Enable DNSSEC](/dns/dnssec/#1-activate-dnssec-in-cloudflare) at Cloudflare. This will automatically add your DS to the zone parent via Cloudflare Registrar.
31+
32+
<Details header="Why you have to disable DNSSEC">
33+
<Render file="why-disable-dnssec" product="dns" />
34+
</Details>

src/content/partials/registrar/next-steps.mdx

Lines changed: 8 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -3,12 +3,20 @@
33

44
---
55

6+
import { Details } from "~/components"
7+
68
## Next steps
79

810
As mentioned in [Review DNS records in Cloudflare](/dns/zone-setups/full-setup/setup/#review-dns-records), when moving your domain to Cloudflare Registrar, you might need to configure your DNS records to correctly point traffic to your web host. Cloudflare automatically scans for common records and adds them to your account's DNS page, but the scan is not guaranteed to find all existing DNS records.
911

1012
Refer to your web host's documentation to learn what type of records you need to configure and where they should point, to avoid downtime.
1113

14+
<Details header="Example">
15+
1216
For example, Netlify asks customers that host websites with them to add a `CNAME` record pointing `<YOUR-DOMAIN>` to `apex-loadbalancer.netlify.com`, and another `CNAME` record pointing `www` to `<YOUR-DOMAIN>.netlify.app`, depending on which one is the primary domain.
1317

1418
![An example of DNS management in Cloudflare's DNS dashboard](~/assets/images/registrar/dns-management.png)
19+
20+
</Details>
21+
22+
You may also want to [enable DNSSEC](/dns/dnssec/#1-activate-dnssec-in-cloudflare).

0 commit comments

Comments
 (0)