Choose how to connect your domain
Compare the two AlphaBlue-supported paths: AlphaBlue-managed DNS or a customer-managed Pages CNAME.
AlphaBlue supports two standard connection methods. We will confirm which one applies to your project. You do not need to choose from technical DNS products or invent a third setup.
If you are unsure, contact AlphaBlue before changing anything. The safest option depends on the website deployment, the address you want and the services already using your domain.
Option A: let AlphaBlue manage DNS
You replace the domain’s current authoritative nameservers with the two Cloudflare nameservers supplied specifically for your domain.
This does not transfer ownership of the domain. You continue to own it through your registrar and remain responsible for renewal, billing and registrant contact information. AlphaBlue manages the DNS zone used to connect the website and preserve the records you disclosed during preparation.
Use this option when:
- your site is deployed as a Cloudflare Worker;
- you want the root domain, such as
example.com, on Cloudflare Pages; - you want AlphaBlue to manage the root domain,
www, HTTPS and website-related DNS; - your current provider allows custom nameservers.
Before you change nameservers, AlphaBlue must prepare the Cloudflare zone and compare its records with the saved source. Do not paste nameservers from another domain: Cloudflare assigns the correct pair to each onboarded zone.
Option B: keep your current DNS and add one Pages CNAME
Your current DNS provider remains authoritative. You add the exact CNAME record supplied by AlphaBlue for a subdomain such as www.example.com or site.example.com.
Use this option when:
- your site is deployed on Cloudflare Pages;
- you accept a specified subdomain as the website address;
- you do not want to change nameservers;
- you can add or edit DNS records at the current provider.
AlphaBlue must register the hostname in the Pages project’s Custom domains section before you add the CNAME. Adding only a CNAME to <project>.pages.dev without that Pages association can fail with a 522 response.
This standard path does not connect the root domain and does not support an ordinary Workers Custom Domain.
Quick comparison
| Requirement | AlphaBlue-managed DNS | Keep DNS and add Pages CNAME |
|---|---|---|
| Domain remains customer-owned | Yes | Yes |
| Customer changes nameservers | Yes | No |
| Cloudflare Pages root domain | Yes | No |
| Cloudflare Pages subdomain | Yes | Yes |
| Cloudflare Workers Custom Domain | Yes | No |
| Existing DNS records must be copied | Yes | No, except the selected hostname may need review |
| AlphaBlue verifies the final result | Yes | Yes |
What if the provider does not allow custom nameservers?
Some domain platforms limit nameserver changes. Wix currently does not allow the nameservers of a Wix-purchased domain to be changed. In that case, the normal choices are:
- keep Wix DNS and connect a Pages subdomain with a supported CNAME; or
- discuss transferring the domain to a registrar that supports the required setup.
Do not begin a transfer solely from this article. A transfer affects renewal, access and timing and must be planned separately with AlphaBlue.
Your next step
Wait for AlphaBlue to send one of these instructions:
Confirmed path: AlphaBlue-managed DNS
Provider guide: <provider>
Assigned nameserver 1: <exact value>
Assigned nameserver 2: <exact value>
or:
Confirmed path: Keep current DNS
Provider guide: <provider>
Record type: CNAME
Name / Host: <exact value>
Target / Value: <exact project>.pages.dev
TTL: Auto / Default
Official references
Technical requirements and Wix limitation last verified: 7 September 2026.