Skip to content

Commit d392065

Browse files
[DNS] Add common pitfalls for NS update (#28898)
* Docs first draft based on tickets MCP * Docs second pass: more concise and no bold * Manual edits: conciseness and accuracy for #restricted-ns-mgmt * Overall review and improve update-nameservers page structure * Check accuracy for ns assignment and improve linking * Remove #platforms-that-already-use-cf
1 parent 346cb18 commit d392065

3 files changed

Lines changed: 22 additions & 8 deletions

File tree

src/content/docs/dns/nameservers/update-nameservers.mdx

Lines changed: 15 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,6 +11,8 @@ To use Cloudflare DNS as an authoritative DNS provider - be it in a [primary (fu
1111

1212
<Render file="nameservers-registrar-callout" product="dns" />
1313

14+
---
15+
1416
## Specific processes
1517

1618
Although Cloudflare will [provide you the nameservers](/dns/nameservers/#authoritative-nameservers-offering) or allow you to create your own [custom nameservers](/dns/nameservers/custom-nameservers/), the final step to make Cloudflare an authoritative DNS provider for your domain may have to be done outside of Cloudflare. If you are not using [Cloudflare Registrar](/registrar/), consider which of the following sections correspond to your use case.
@@ -50,10 +52,22 @@ Delegation means that `shop.example.com` has specific `NS` records set up for it
5052

5153
If that is the case, when setting up your zone in Cloudflare or opting for a different set of [nameservers](/dns/nameservers/), you have to update the `NS` records in the parent domain, and not at the registrar.
5254

55+
---
56+
57+
## Restricted nameserver management
58+
59+
Some providers act as registrars but do not expose nameserver settings. If you cannot change nameservers at your registrar or hosting platform, you can either:
60+
61+
- Transfer your domain to a registrar that allows nameserver management.
62+
- Transfer your domain to Cloudflare Registrar. All domains on [Cloudflare Registrar](/registrar/) automatically use Cloudflare nameservers.
63+
- Use a [CNAME setup (partial)](/dns/zone-setups/partial-setup/) instead. This option does not require nameserver changes and is available on Business and Enterprise plans.
64+
65+
---
66+
5367
## Further guidance
5468

5569
This page covers specific workflows that customers who do not use Cloudflare Registrar[^1] might have to follow to update their domain nameservers. For complete tutorials, refer to the pages below. Full setup is the most common option, and the only one available for customers on the Free or Pro plans.
5670

5771
<DirectoryListing folder="/dns/zone-setups/" />
5872

59-
[^1]: If you acquired your domain from Cloudflare Registrar, your domain already uses and must remain on Cloudflare nameservers. For details, refer to [Registrar](/registrar/faq/#can-i-change-my-nameservers).
73+
[^1]: If you acquired your domain from Cloudflare Registrar, your domain already uses and must remain on Cloudflare nameservers. For details, refer to [Registrar](/registrar/faq/#can-i-change-my-nameservers).

src/content/docs/dns/zone-setups/reference/domain-status.mdx

Lines changed: 6 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,6 @@
11
---
22
pcx_content_type: reference
33
title: Zone status
4-
54
---
65

76
Review information on the different statuses that your [zone](/dns/concepts/#zone) can have after you [add your website or application](/fundamentals/manage-domains/add-site/) to Cloudflare.
@@ -59,8 +58,8 @@ Cloudflare responds to DNS queries for pending zones on the assigned Cloudflare
5958

6059
### Causes
6160

62-
* [Primary setup (Full)](/dns/zone-setups/full-setup/): You have either not [changed your authoritative nameservers](/dns/nameservers/update-nameservers/) or your change has not yet been authenticated by Cloudflare.
63-
* [CNAME setup (Partial)](/dns/zone-setups/partial-setup/): You have either not added the verification TXT record to your authoritative DNS provider or the record has not yet been authenticated by Cloudflare.
61+
- [Primary setup (Full)](/dns/zone-setups/full-setup/): You have either not [changed your authoritative nameservers](/dns/nameservers/update-nameservers/) or your change has not yet been authenticated by Cloudflare.
62+
- [CNAME setup (Partial)](/dns/zone-setups/partial-setup/): You have either not added the verification TXT record to your authoritative DNS provider or the record has not yet been authenticated by Cloudflare.
6463

6564
After you add your domain, Cloudflare performs checks on a schedule to confirm you have updated your nameservers. The first check occurs after 60 seconds and the following attempts happen at gradually increased intervals. You can re-trigger the check [via API](/api/resources/zones/subresources/activation_check/methods/trigger/) or on the Dashboard, in the respective domain [Overview page](https://dash.cloudflare.com/?to=/:account/:zone/).
6665

@@ -99,6 +98,10 @@ You can also [manually remove](/fundamentals/manage-domains/remove-domain/) your
9998

10099
Your zone has been archived. Cloudflare still responds to DNS queries for deleted zones on the assigned Cloudflare nameserver IPs (for non-deleted DNS records) and you can re-add the domain to Cloudflare by following the [regular onboarding flow](/fundamentals/manage-domains/add-site/).
101100

101+
:::caution[New nameserver assignment]
102+
When you re-add a previously deleted domain, Cloudflare assigns a new nameserver pair as a security measure. If you are not using Cloudflare Registrar, make sure to [update your registrar](/dns/nameservers/update-nameservers/) with the new nameservers after re-adding the domain. Refer to [nameserver assignment](/dns/nameservers/nameserver-options/#assignment-method) for details.
103+
:::
104+
102105
After being deleted for seven days, zones are automatically [purged](#purged).
103106

104107
## Purged

src/content/docs/dns/zone-setups/removal.mdx

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -3,19 +3,16 @@ title: Zone removal
33
pcx_content_type: concept
44
sidebar:
55
order: 12
6-
76
---
87

98
If domains on Free zones remain in the [Pending](/dns/zone-setups/reference/domain-status/#pending) or [Moved](/dns/zone-setups/reference/domain-status/#moved) status for too long, Cloudflare automatically removes them from your account and the Cloudflare network. Refer to [zone statuses](/dns/zone-setups/reference/domain-status/) for more details.
109

1110
You can also [manually remove a domain](/fundamentals/manage-domains/remove-domain/) from Cloudflare.
1211

13-
If you need to re-add a domain to your account, follow the [regular onboarding flow](/fundamentals/manage-domains/add-site/).
12+
If you need to re-add a domain to your account, follow the [regular onboarding flow](/fundamentals/manage-domains/add-site/). Cloudflare will assign a new nameserver pair when you re-add the domain, so you must [update your registrar](/dns/nameservers/update-nameservers/) with the new nameservers. Refer to [nameserver assignment](/dns/nameservers/nameserver-options/#assignment-method) for details.
1413

1514
:::caution[Purged zones]
1615

17-
1816
By default, your zone will be automatically purged seven days after the removal. In this case, even if you re-add the domain to the same Cloudflare account, none of the zone settings are expected to be restored. Refer to [zone statuses](/dns/zone-setups/reference/domain-status/) for more details.
1917

20-
2118
:::

0 commit comments

Comments
 (0)