Attaching a custom domain

The short version

1. From the cabinet's Domains panel, click Add domain.
2. Enter the bare domain (e.g. mycasino.com).
3. The cabinet shows the CNAME you need to add at your DNS provider.
4. Add the CNAME. We poll DNS until it propagates (usually under a minute).
5. Hit Deploy — the bundle uploads with the new domain wired up.

DNS provider detection

When you enter a domain, the cabinet runs a DoH lookup against the apex NS records. If your DNS is on Cloudflare we surface a one-click "Add via CF API" path; if it's elsewhere (Namecheap, GoDaddy, Route53, …) we show provider-specific copy-paste instructions for the CNAME.

Domains already inside the customer's Cloudflare account skip the manual step — the narrow API token we hold scopes to Pages only, but the cabinet hints at the "import to your account" path if you want full CF DNS control.

Multi-host topology

A single tenant can serve different locales on different domains. For example:

• RU locale on mycasino.ru
• EN locale on mycasino.com

Both domains attach to the same Pages project. Under the hood the bundle stores RU at the bundle root and EN at /en/; a _redirects file rewritesmycasino.com/* onto /en/:splat with a 200 (not a 3xx — the URL stays clean for the visitor).

CF Zone Rules for /go/<slug> routing

For tenants on TDS traffic mode (CTAs go through /go/<slug>?utm_source=signin|signup|…) on a multi-host bundle, the platform automatically provisions a CF Zone URL Rewrite rule per attached domain so the affiliate paths resolve at the edge before Pages' own _redirects parser runs. This is the only way to make hostname-aware /go/ routing survive Pages' default-host behaviour.

SSL

Cloudflare Pages issues Universal SSL certificates automatically as soon as the CNAME propagates. No action needed on your side — the site is HTTPS-only by default.