Custom domain

Where: Setup → Domain

Serve your event on your own web address instead of a platform URL.

Start this early

DNS changes are the one part of setup you cannot speed up. Propagation ranges from a few minutes to a full day depending on your provider. Begin on day one and let it settle while you do everything else.

What you need first

• A domain you own, or a subdomain of one — bought from a provider such as GoDaddy, Namecheap or Cloudflare.
• Access to that provider's DNS settings.

If someone else in your organisation controls the domain, involve them now. This step needs their access, and the back-and-forth is usually longer than the propagation.

Connecting a domain

1. Add the domain here. Use Add Custom Domain and enter it exactly as you want it — ride.example.com or example.com.

2. Add the DNS records at your provider. The screen shows you exactly what to add, with a copy button for each value. There are two:

Purpose	Record
Point traffic at the platform	An A record, with the Host / Name and Points to (IP) shown on screen
Prove you own the domain	A TXT record with the verification token shown on screen

Copy the values from the screen rather than from any documentation, including this page — the IP and token are specific to your event.

3. Wait. Minutes to a day.

4. Verify. Come back and run the verification. It checks both records.

Checking status

Each connected domain shows two indicators:

• Ownership Verified — the TXT record was found. The domain is yours.
• DNS Connected — the A record is correct. Traffic reaches the platform.

Both must be satisfied before the domain serves your event.

If one is still failing after a day, the record almost certainly did not save the way you expected at your provider. Common causes: the host field wanting @ rather than the full domain, a trailing dot, or an existing conflicting record you needed to replace rather than add alongside.

Site Version

Each domain shows which version of the event site it serves.

Leave this as configured unless your technical contact tells you otherwise. It is how the platform runs more than one product version at a time, and changing it changes which codebase serves your participants.

SSL

The secure padlock is issued automatically once the domain verifies. You do not buy or install a certificate.

It can take a short while after verification. If the domain loads but warns about security, give it an hour before escalating.

Subdomains

Using a subdomain — ride.example.com rather than example.com — is usually the better choice. It leaves your main website untouched, and the DNS change is contained to a record that did not previously exist.

It is also easier to get approved internally, since it does not require touching the organisation's primary domain.

Multiple domains

You can connect more than one to the same event. Useful when you have both example.com and example.org, or a short campaign domain alongside a descriptive one.

Troubleshooting

Verification keeps failing. Check the record at your provider matches character for character, including the host field. Many providers append your domain automatically, so entering the full domain produces ride.example.com.example.com.

The domain loads the wrong thing. An older A record is still present. Replace it rather than adding a second one.

It worked, then stopped. Check the domain has not expired, and that the DNS records still exist — some providers reset records when other settings change.