03 — Custom Domain

Connect your own domain (e.g., myapp.com) to your Pages project. SSL is automatic. Works with any registrar.

Prerequisites

You need a domain name and access to its DNS settings. It doesn't matter where you registered it—Namecheap, GoDaddy, Cloudflare Registrar, etc. This process works the same.

The Two Paths

Path A: Your Domain is Already at Cloudflare

If you registered your domain through Cloudflare Registrar or moved your DNS to Cloudflare:

  1. Go to dash.cloudflare.com and select your domain
  2. Go to Pages > Your Project > Custom domain
  3. Enter your domain (e.g., myapp.com)
  4. Click Continue

Cloudflare auto-provisions SSL within 2 minutes. Your domain now points to your Pages project. Done.

Path B: Your Domain is Elsewhere (Namecheap, GoDaddy, etc.)

You need to add a CNAME record at your registrar.

Step 1: Get Your Pages Deployment URL

In the Cloudflare Dashboard, under your Pages project, you'll see:

Live URL: drklynx-m-abc123def456.pages.dev

Copy this URL (just the domain, without https://).

Step 2: Add a CNAME Record

Log in to your domain registrar (Namecheap, GoDaddy, etc.) and find the DNS settings.

Add a new CNAME record:

Field Value
Name @ (for root) or www (for www.example.com)
Type CNAME
Value drklynx-m-abc123def456.pages.dev
TTL 3600 (or default)

Example (Namecheap):

  1. Log in to Namecheap
  2. Go to Domain List > your domain > Manage
  3. Click DNS
  4. Find the CNAME row with Name = @
  5. Change the Value to drklynx-m-abc123def456.pages.dev
  6. Save

Step 3: Wait for Propagation

DNS changes take 24–48 hours to propagate globally, but often only 5–15 minutes for your ISP. You can check propagation:

nslookup myapp.com
# or
dig myapp.com

Once it resolves to Cloudflare's servers, you're done.

Step 4: Tell Cloudflare About Your Domain (Optional but Recommended)

Even if your registrar isn't Cloudflare, you can move your DNS to Cloudflare to speed things up and unlock other features:

  1. Go to dash.cloudflare.com > + Add site
  2. Enter your domain
  3. Choose the free plan (or upgrade later)
  4. Cloudflare gives you two nameserver addresses
  5. Go back to your registrar and update the nameservers to Cloudflare's
  6. Wait 24–48 hours for the change to propagate
  7. Return to Cloudflare and click Done, nameservers are set

Once your domain is at Cloudflare, SSL auto-provisions within minutes.

SSL Certificate (HTTPS)

Cloudflare automatically provisions and renews a free SSL certificate for your domain. No action needed.

Your site will be accessible at:

  • https://myapp.com
  • https://www.myapp.com (if you created a www CNAME)

HTTP traffic is automatically redirected to HTTPS.

Apex Domain vs. Subdomain

Apex (Root Domain)

myapp.com (no www)

Use a CNAME at the @ record. Works fine.

www Subdomain

www.myapp.com

Use a CNAME at the www record.

Both

If you want myapp.com and www.myapp.com to work, create two CNAME records:

  • Name @ → CNAME drklynx-m-abc123def456.pages.dev
  • Name www → CNAME drklynx-m-abc123def456.pages.dev

Troubleshooting

"DNS Not Propagating After 24 Hours"

  1. Check your CNAME is correct: nslookup myapp.com
  2. Make sure you saved the DNS record at your registrar
  3. If using Cloudflare DNS, verify nameservers are set: nslookup -type=ns myapp.com
  4. Wait another 24 hours (sometimes ISP caches are slow)
  5. If still stuck, email support@drklynx.com with your domain and Pages project name

"SSL Certificate Not Provisioning"

Cloudflare needs to verify domain ownership. This usually happens automatically once DNS resolves. If it's been 30 minutes and SSL hasn't provisioned:

  1. Double-check your CNAME is exactly: drklynx-m-abc123def456.pages.dev
  2. Make sure DNS is resolving: nslookup myapp.com
  3. In the Cloudflare Dashboard, under your domain, go to SSL/TLS > Certificate and look for any error messages

"Redirection Loop or Page Doesn't Load"

If you get an error, your CNAME might be pointing to the wrong Pages project. Check:

  1. Pages project name: drklynx-m-abc123def456 (matches your customer ID)
  2. CNAME value is exactly: drklynx-m-abc123def456.pages.dev

Purging Cache After Deploy

After you deploy changes to your Pages project, the edge cache might serve the old version for up to 60 seconds. To force an immediate refresh:

  1. Go to your domain on dash.cloudflare.com
  2. Click Caching > Purge Cache
  3. Choose Everything and click Purge

Your new deploy is live instantly.

What to Read Next

Getting help: Email support@drklynx.com or check status.drklynx.com.