Keep your DNS provider and add a Pages CNAME

Use this path only when AlphaBlue confirms that your website is deployed on Cloudflare Pages and will use a subdomain such as www.example.com or site.example.com.

Your current provider remains responsible for authoritative DNS. You add one CNAME record using values prepared for your project.

If the selected Name or Host already has any A, AAAA, CNAME, ALIAS, forwarding or website-builder setting, stop and contact AlphaBlue. Do not delete the existing setting yourself.

AlphaBlue must prepare Pages first

Before you add the DNS record, AlphaBlue will:

1. deploy the correct production version to Cloudflare Pages;
2. open the Pages project’s Custom domains section;
3. register your exact hostname;
4. send you a DNS setting card.

Adding only a CNAME to a pages.dev address without first associating the hostname in Pages can result in a 522 error.

Read your setting card exactly

It will look like this:

Record type: CNAME
Name / Host: <exact subdomain label>
Target / Value / Points to: <exact project>.pages.dev
TTL: Auto / Default

The words used by your provider may differ:

AlphaBlue card	Provider may call it
Name	Host, Hostname, Alias
Target	Value, Data, Answer, Points to
TTL	Time to live

Enter the exact values from your card. Do not add https://, /, a page path or quotation marks. Unless the provider-specific guide says otherwise, the Name field normally contains only the subdomain label such as www, not the full domain.

Add the CNAME

1. Sign in to the account that currently manages active DNS.
2. Open the correct domain’s DNS record editor.
3. Search for an existing record with the same Name or Host.
4. If any matching record exists, stop and send a screenshot to AlphaBlue.
5. Select Add record or the provider’s equivalent.
6. Choose CNAME.
7. Enter the exact Name / Host from the AlphaBlue card.
8. Enter the exact Target / Value from the card.
9. Leave TTL at Auto or the provider default unless AlphaBlue specifies another value.
10. Review the fields before saving.
11. Save once.
12. Take a screenshot showing the new record and send it to AlphaBlue.

Do not edit MX, TXT, DNSSEC or unrelated records. Do not reset the DNS zone.

Limits of this path

This standard setup:

• supports a Cloudflare Pages subdomain;
• does not move DNS management to AlphaBlue;
• does not connect the root domain through the standard external-DNS Pages path;
• does not support an ordinary Cloudflare Workers Custom Domain;
• may leave example.com separate from www.example.com unless another agreed redirect is configured.

If the root domain must be the primary address, discuss AlphaBlue-managed DNS before proceeding. Do not assume a registrar forwarding feature provides the same HTTPS and reliability behaviour.

After saving

Wait for AlphaBlue to verify the public CNAME, Pages activation and HTTPS certificate. Do not recreate the record or add extra A records while waiting.

Contact AlphaBlue if the provider rejects the target, automatically changes the hostname, shows a conflict or asks you to remove another record.

Official reference

• Cloudflare Pages custom domains

Technical requirements last verified: 7 September 2026.