Understand DNS records and domain verification
Why CourtBeam asks for a DNS record and how to resolve common verification delays.
What the record proves
The DNS record proves that your club controls the domain. CourtBeam uses that proof before activating the booking site on the custom address.
Common problems
- The record was added to the wrong DNS provider.
- The host field included the full domain when the provider expects only the subdomain.
- A proxy or redirect is masking the expected record.
- An old record is still cached.
- The domain is already attached to another site or service.
Escalate with evidence
If the record is correct and verification remains pending, send support the domain, the record type and host, and a screenshot with unrelated DNS records redacted. Never send provider passwords.
Was this article helpful?
Still stuck?
Contact support Send us the step that failed and the reference you see. We will help you pick it up.