How to connect your domain
Point a domain you own at ByteAlley so visitors land directly on your funnel — for example mycoolfunnel.com instead of a ByteAlley link.
The short version
- 1. Add your domain in ByteAlley's Settings → Custom Domains.
- 2. Copy the two DNS records ByteAlley shows you (one to point your domain at us, one to prove you own it).
- 3. Paste them into your DNS provider (this guide walks through Cloudflare).
- 4. Wait 1–5 minutes, then click Verify now. Done.
Why two records?
ByteAlley needs to know two things before it can serve your funnel on your domain. The first record points web traffic at our servers so visitors actually reach ByteAlley. The second record proves you own the domain — without it, anyone could try to attach your-business.com to their ByteAlley account.
Both records are added at your DNS provider (whoever you bought the domain from, or wherever you currently manage its DNS — typically Cloudflare, Namecheap, GoDaddy, Google Domains, etc.).
Step 1 — Decide: apex or subdomain?
How you connect depends on which URL you want visitors to type:
Apex (root domain)
e.g. mycoolfunnel.com
137.184.23.133Subdomain
e.g. funnel.mybusiness.com
funnels.trybytealley.comTip: If your business already has a website at your apex (say mybusiness.com is your company site), use a subdomain like funnel.mybusiness.com instead so you don't replace your main site.
Step 2 — Add the records in Cloudflare
These steps use Cloudflare's current dashboard. Other providers (Namecheap, GoDaddy, Google Domains) work the same way — the field names are nearly identical, just in a different layout.
Open your domain's DNS settings
In the Cloudflare dashboard, click the domain you want to connect. In the left sidebar, click DNS, then Records. You'll see a table of any existing records.
Add the first record (points traffic at us)
Click the blue Add record button and fill in:
| Type | A (for apex) or CNAME (for subdomain) |
| Name | @ for apex, or the subdomain part (e.g. funnel) |
| Target / IPv4 address | the A record IP or CNAME target shown in the ByteAlley dashboard |
| Proxy status | DNS only (gray cloud) — see warning below |
| TTL | Auto |
Click Save.
Add the second record (the verification TXT)
Click Add record again. This time:
| Type | TXT |
| Name | _bytealley (Cloudflare auto-completes the full hostname) |
| Content | the bytealley-verification=... string from the dashboard |
| TTL | Auto |
Click Save. You'll now have two new records in the list.
Critical: leave the proxy off (gray cloud)
Cloudflare's signature feature is its orange cloud proxy that puts Cloudflare in front of your traffic. For ByteAlley custom domains, this must be off — set to DNS only (gray cloud icon). If you leave it proxied:
- ByteAlley can't get a TLS certificate for your domain, so visitors see a "your connection is not private" warning.
- Even if the cert worked, requests get terminated at Cloudflare's edge instead of reaching us — the funnel never loads.
You can re-enable Cloudflare's proxy later if you set up a more advanced configuration (Cloudflare Origin certificate + Full Strict mode), but for the default setup keep it gray.
Step 3 — Wait, then verify
DNS changes take anywhere from a few seconds to ~10 minutes to propagate worldwide. ByteAlley checks your records every few minutes automatically, but if you don't want to wait, go back to Settings → Custom Domains and click Verify now on your domain.
Once the status flips to Active, open https://your-domain.com in a new tab — your funnel should load with a valid HTTPS lock icon.
Tip: The first time you load the page on a new domain, it can take 5–10 seconds while ByteAlley provisions an HTTPS certificate for you. Subsequent loads are instant.
Troubleshooting
My domain has been stuck on 'Waiting on DNS' for 30 minutes.
Open a terminal and run dig +short your-domain.com. If it returns blank or a different IP than the one shown in the dashboard, your A record hasn't propagated (or wasn't saved correctly). Double-check in Cloudflare that the record exists with the exact value from ByteAlley, and that it's set to DNS only, not proxied.
It says 'Verifying ownership' but the TXT record is set.
Run dig TXT _bytealley.your-domain.com +short in a terminal. The output must exactly match the bytealley-verification=... string from ByteAlley — including the equals sign. A common mistake is pasting with surrounding quotes; some DNS providers add the quotes for you, so don't paste them yourself.
Visitors see 'Your connection is not private' in the browser.
Cloudflare's proxy is on (orange cloud). Switch it to DNS only (gray cloud), wait a couple of minutes, and try again.
My funnel loads at the apex but not the www version.
The www version needs its own record. Add a second CNAME record: www → your-domain.com (your own apex). Cloudflare will follow the chain.
I switched my homepage funnel and the old one is still showing.
We cache the resolution for a minute to keep things fast. Wait 60–90 seconds and refresh in a private window (to bypass your browser's own cache).
Still stuck?
If your domain still isn't connecting after following the steps, reply to your welcome email or message support with your domain name and we'll take a look.