Introduction

A nameserver cutover can look complete in the registrar account while the Cloudflare zone still shows Pending Setup. The DNS records may already exist inside Cloudflare, but the zone does not become active because the parent delegation for the domain still does not match what Cloudflare expects.

Treat this as a delegation problem instead of a zone-content problem. Start by checking the exact nameservers assigned by Cloudflare against what the registry and registrar are actually publishing, because a zone will stay in Pending Setup if the live delegation still points anywhere else.

Symptoms

  • The Cloudflare dashboard still shows Pending Setup after the nameserver cutover
  • DNS records are present in Cloudflare, but live traffic does not use them
  • The assigned Cloudflare nameservers were entered, but the zone never becomes active
  • Public delegation checks still show old, mixed, or incomplete nameserver values
  • Different control panels show different nameserver states for the same domain
  • The issue started after a registrar change, nameserver update, or DNS provider migration

Common Causes

  • The registrar delegation does not exactly match the Cloudflare nameservers assigned to the zone
  • Only one nameserver was updated, or old nameservers are still mixed with the new pair
  • The nameserver change was made in the wrong registrar or reseller account
  • The registrar interface saved the request, but the registry is still publishing the previous delegation
  • The domain is under transfer, lock, or pending approval, so the nameserver change did not finalize
  • Troubleshooting focused on Cloudflare DNS records instead of the parent nameserver delegation

Step-by-Step Fix

  1. Open the Cloudflare zone and copy the exact nameservers assigned to that domain, because you need the precise pair before comparing anything at the registrar.
  2. Check the domain at the authoritative registrar or reseller account and confirm the live nameserver entries match Cloudflare exactly, because even one extra or incorrect entry will keep the zone from activating.
  3. Verify the parent delegation with a public WHOIS or DNS delegation lookup, because the registry view matters more than what one control panel says was saved.
  4. Make sure you are editing the nameservers in the correct registrar account, because domains managed through resellers or recent transfers are often changed in the wrong place.
  5. Remove any old or mixed nameserver entries and save only the exact Cloudflare pair assigned to the zone, because partial cutovers do not satisfy Cloudflare activation.
  6. Check for pending registrar confirmations, transfer status, or domain locks that might prevent the update from reaching the registry, because a nameserver request can appear submitted while never becoming live.
  7. Wait for the delegation change to publish, then recheck the parent nameservers instead of only refreshing the Cloudflare dashboard, because the zone cannot leave Pending Setup until the registry change is visible.
  8. Once Cloudflare shows the zone as active, test the live DNS records and any proxied hostnames, because activation alone does not confirm the migrated zone content is correct.
  9. Document the assigned Cloudflare nameservers, registrar account used, and cutover timestamp, because nameserver delegation problems are much easier to troubleshoot with an exact activation record.