Guide7 min readUpdated 7 Sept 2026

Cloudflare Registrar: connect your domain to AlphaBlue

Use scoped Cloudflare access or add a Pages CNAME without trying to replace Cloudflare Registrar nameservers.

Cloudflare Registrar is different from most registrars in this course. A domain registered there must continue using Cloudflare authoritative nameservers. You cannot replace them with another DNS provider’s nameservers while the registration remains at Cloudflare.

Do not try to copy nameservers from another AlphaBlue zone. Contact AlphaBlue before changing account members, DNS records, Pages or Workers settings.

Provider instructions last verified: 7 September 2026, against Cloudflare’s official documentation.

Supported paths

AlphaBlue path Support What changes
AlphaBlue-managed DNS Operator-assisted Keep Cloudflare nameservers; agree the account and hosting placement, then grant scoped access if appropriate
Keep customer DNS and add a Pages CNAME Supported Customer adds one CNAME in the existing Cloudflare zone after AlphaBlue registers the Pages hostname

Path A: AlphaBlue-managed DNS

This is not a nameserver-change tutorial. The zone already uses Cloudflare DNS, and the correct AlphaBlue workflow depends on where the Pages project or Worker will live.

AlphaBlue will first confirm whether to:

  • operate the site in the customer’s Cloudflare account with appropriately scoped access; or
  • use another agreed account or registration arrangement through a separate, documented handover.

If scoped member access is appropriate, the Cloudflare account’s Super Administrator can:

  1. sign in to the Cloudflare dashboard;
  2. open Manage Account → Members;
  3. select Invite;
  4. enter the AlphaBlue operator email supplied for the project;
  5. scope access to the specific domain and required resources;
  6. use the least-privileged roles confirmed by AlphaBlue, such as domain-level DNS access and only the required Workers／Pages access;
  7. review the summary before sending the invitation.

Do not grant billing access or Super Administrator - All Privileges unless a separately approved operational requirement makes it necessary. AlphaBlue will confirm the required roles because DNS-only permission may not be enough to attach a Pages project or Worker located in another account.

Path B: keep the current Cloudflare zone and add a Pages CNAME

Only continue after AlphaBlue has registered the exact subdomain in the Pages project’s Custom domains section and supplied the setting card.

  1. Sign in to Cloudflare and select the account and domain.
  2. Open DNS → Records.
  3. Search for the exact Name supplied by AlphaBlue.
  4. If an A, AAAA or CNAME already uses that name, stop and send a screenshot.
  5. Select Add record.
  6. Choose CNAME.
  7. Enter the exact Name and <project>.pages.dev target from the AlphaBlue card.
  8. Use the Proxy status specified by AlphaBlue; do not guess between proxied and DNS only.
  9. Keep TTL at Auto unless instructed otherwise.
  10. Select Save, then send AlphaBlue a screenshot of the record.

Do not edit MX, TXT, CAA, DNSSEC or unrelated records.

Stop and contact AlphaBlue if

  • the domain is not visible in the expected Cloudflare account;
  • the account or role requested does not match the project instruction;
  • the hostname already has an A, AAAA or CNAME;
  • Cloudflare reports that the domain belongs to another Pages project or Worker;
  • you see a registrar hold or unverified registrant email warning.

Official sources