In a Cloudflare full setup, what must change at the registrar to activate a zone, and why does it stay Pending until then?
answer
- two assigned names, copied exactly
- old provider's nameservers come out
- Pending Nameserver Update
- activation checks on a schedule
- Free plan: deleted after 28 days
basics
~20 sReplace the domain's nameservers at the registrar with exactly the two Cloudflare nameservers assigned to the zone. Until the parent zone delegates to them and Cloudflare's activation check sees it, the zone stays Pending Nameserver Update and proxies nothing.
solid answer
~40 sAfter you add the domain, Cloudflare scans for common records and assigns two nameservers of the form `<name>.ns.cloudflare.com`. You review the imported records, because the scan does not find everything, turn DNSSEC off at the registrar if it is on, and then replace every existing nameserver there with exactly the assigned pair. Cloudflare runs activation checks, the first about 60 seconds after the zone is added and then at growing intervals, and you can request an earlier one from the zone's **Overview** page. While the parent zone still lists other nameservers, the status stays **Pending Nameserver Update**: Cloudflare answers queries on the assigned nameservers, but nothing is proxied, cached or filtered. A Free-plan zone left pending for 28 days is deleted; a zone on a paid plan stays pending.
go deeper
Recall the sequence: add the zone, review records, change the nameservers at the registrar to the exact assigned pair, then wait for Pending Nameserver Update to turn Active.
Explain what the activation check looks at, why only the assigned names may be listed, and how statuses move from Initializing through Pending to Active or Moved.
Show you can verify the delegation at the parent with dig +trace, spot a stale DS, and plan a cutover with lowered TTLs and both providers serving identical answers.
Talk about owning the cutover: who holds registrar access, how record changes freeze during the switch, and what rollback looks like if the new zone misses records.
## What a full setup is In a **full setup** (Cloudflare also calls it a **primary setup**), Cloudflare becomes the domain's authoritative DNS provider: resolvers ask Cloudflare's nameservers for every record in the zone. It is the most common setup and the only one available on the **Free** and **Pro** plans. Nothing about it takes effect until the world is told to ask Cloudflare, and that instruction lives in one place: the delegation the registrar publishes in the parent zone (for `example.com`, the `com` zone). ## The steps, in order 1. **Add the domain.** Enter the apex (`example.com`) and pick a plan. Cloudflare runs a **records quick scan** that imports common record types and names. 2. **Review the records.** The quick scan works from common patterns, so it misses unusual names, such as a hostname like `my-store1900` or a DKIM key published under a custom selector. Compare the imported zone with the old provider's, or import a full zone file through **Import and Export** on the **DNS Records** page. 3. **Read the assigned nameservers** on the zone's **Overview** page. A standard full setup gets two names of the form `<name>.ns.cloudflare.com`. They are fixed once the zone exists; not even Cloudflare Support can change them. 4. **Turn off DNSSEC at the registrar** if the domain has it, before touching the nameservers. A DS record left over from the old provider breaks validation after the switch. 5. **Replace the nameservers at the registrar**: remove every existing one and add the assigned pair, copied exactly. 6. **Wait for activation.** Registrars can take up to 24 hours to publish the change. Cloudflare emails you when the zone becomes **Active**. ## What the zone statuses mean | Status | What is true | | --- | --- | | Initializing (shown as **Finish setup**) | Added in the dashboard, no plan chosen; Cloudflare answers no queries. Deleted after 28 days. | | Pending (**Pending Nameserver Update**) | Cloudflare answers on the assigned nameservers, but the zone cannot proxy traffic, so caching and security settings do not apply yet. | | Active | The delegation was confirmed; proxied records and zone settings take effect. | | Moved | An active zone whose Cloudflare nameservers disappeared from its `NS` records after repeated checks. | Cloudflare checks a pending zone on a schedule: the first check runs about 60 seconds after the zone is added, later ones at gradually longer intervals, and you can trigger one from the **Overview** page or the API. A **Free-plan** zone that is not activated within **28 days** is deleted automatically; a pending zone on a paid plan stays pending until it is activated, removed or its plan is removed. Do not send production traffic through a pending zone. ## Why a zone stays pending - **Other nameservers still listed.** Without multi-provider DNS turned on, the parent must list only the assigned Cloudflare nameservers; a leftover name from the old provider fails the check. - **A typo or the wrong pair.** Names typed by hand (`cloudfare.com`) or a pair copied from another zone in the account do not match. Each zone's assignment is its own. - **The change never published.** It was not saved, went to another domain, or the domain is locked by a transfer or redemption state. - **A stale DS record** from the previous provider is still at the registrar. Check what the parent actually publishes, not what the registrar's page shows, with `dig +trace example.com NS +noall +authority +nodnssec`; the last hop must show only the assigned names. ## Keeping the cutover quiet - **Lower record TTLs at the old provider ahead of time**, at least one old TTL before the switch, so resolvers drop cached answers quickly afterwards. - **Keep the old provider's zone serving and unchanged** until caches have moved over; resolvers holding its cached `NS` records keep asking it for a while. - **Mirror late changes.** A record added at the old provider after onboarding must be added in Cloudflare too. - **Do not preset Cloudflare's nameservers** at the registrar before the zone exists: Cloudflare then assigns a different pair to prevent hijacking, and re-adding a deleted domain does the same. A domain registered through **Cloudflare Registrar** already uses Cloudflare as its authoritative DNS, so none of the registrar steps apply to it.
- Why can a new Cloudflare zone get different nameservers from the account's other zones?Assignment favours the same names across an account, but a conflict changes them: the same zone added to another Cloudflare account, nameservers preset at the registrar before the zone was created, or a deleted domain added again. Once the zone exists the pair is fixed. Enterprise accounts can set DNS zone defaults or account custom nameservers to make assignment more consistent.
- The registrar's page shows Cloudflare's nameservers, yet the zone is still pending. What do you check next?Query the parent directly with `dig +trace example.com NS +noall +authority +nodnssec`: the last hop must list only the assigned pair. If it does, run `dig DS example.com` for a stale DS from the old provider, then trigger an activation check from the **Overview** page. If the parent shows other names, the registrar never published the change.
It is like a change of address with the post office: the new mailbox is ready the day you rent it, but letters keep going to the old one until the post office's own record names the new address.
- Listing Cloudflare's pair beside the old provider's nameservers gives a safe overlap.
- Any Cloudflare nameserver pair already used in the account will work for a new zone.
- The records quick scan imports every record, so there is nothing to review.
- A pending zone already gets caching and WAF protection for proxied records.
- Setting Cloudflare's nameservers at the registrar first makes activation faster.
Assumes Cloudflare as of 2026-10-10, where nameservers preset at the registrar before the zone exists no longer carry over: Cloudflare assigns the new zone a different pair.