Guide7 min readUpdated 7 Sept 2026

Let AlphaBlue manage your domain's DNS

A controlled handover for DNS management while you keep ownership, renewal and registrar control of the domain.

This path lets AlphaBlue manage the DNS zone used by your website. Your domain is not transferred to AlphaBlue: it stays in your registrar account, and you remain responsible for ownership, renewal, billing and registrant contact details.

Do not begin until AlphaBlue says the replacement DNS zone is ready. Changing nameservers before existing records are checked can interrupt email and other services.

What AlphaBlue prepares first

Before asking you to change anything, AlphaBlue will:

  1. add your root domain to the correct Cloudflare account;
  2. review the records Cloudflare found;
  3. compare them with the screenshots or export you supplied;
  4. add missing records needed for disclosed email and connected services;
  5. check whether DNSSEC needs a coordinated change;
  6. provide the two exact Cloudflare nameservers assigned to your domain;
  7. tell you which provider-specific guide to follow.

Cloudflare’s automatic scan is a starting point, not proof that every record was copied.

What you change at the registrar

The exact menu differs by provider, but the action is the same:

  1. Sign in to the registrar account yourself.
  2. Open the correct domain.
  3. Find Nameservers, Name servers or Domain Nameservers.
  4. Choose the option for custom or external nameservers.
  5. Remove the old authoritative nameserver values only after AlphaBlue confirms readiness.
  6. Enter the two values supplied by AlphaBlue, one per field or line.
  7. Check spelling carefully. Do not add https://, a path, an IP address or spaces.
  8. Save the change.
  9. Complete the provider’s account verification if required.
  10. Take a screenshot showing the saved nameservers and send it to AlphaBlue.

Use only the values in your project instruction. Do not copy example values or Cloudflare nameservers from another domain.

Do not change the DNS record list at the old provider

When nameservers switch, the active DNS zone moves to Cloudflare. You normally do not need to delete old records from the registrar’s DNS editor. Keeping the old list temporarily also gives the team a reference during verification.

Do not select Reset DNS, restore a hosting preset or delete all records.

DNSSEC may require a separate coordinated step

If the domain currently has DNSSEC or a DS record, wait for AlphaBlue’s exact instruction. In a normal migration, the old DS record must stop validating the previous provider before the new nameserver chain is used. Changing nameservers in the wrong order can produce SERVFAIL even when the DNS records look correct.

This is a stop condition, not a self-service troubleshooting task.

After you save

Do not repeatedly switch nameservers or edit Cloudflare DNS. AlphaBlue will verify:

  • the registrar publishes only the assigned Cloudflare nameservers;
  • the Cloudflare zone becomes Active;
  • the website hostname is connected to the correct Pages project or Worker;
  • HTTPS certificates are active;
  • root and www behaviour matches the agreed primary address;
  • disclosed email and other critical records still resolve.

Your setup is complete only after AlphaBlue sends the completion confirmation.

Contact AlphaBlue immediately if

  • the provider will not accept the nameservers;
  • the screen asks for IP addresses or glue records;
  • you see a DNSSEC or DS warning;
  • the provider says email or hosting will be disconnected;
  • the saved values are different from what you entered;
  • the website or email stops working.

Send a screenshot of the full message. Do not send a password, one-time code or recovery code.

Official references

Technical requirements last verified: 7 September 2026.