Skip to main content
Help centre
White-label

Connecting a custom domain (yourclub.com)

Pro and Enterprise plans can map a custom domain. Add a CNAME, we provision SSL automatically — usually live within an hour.

5 min read·Updated 2026-04-26

What you need

  • A domain you own (e.g., book.yourclub.com — usually a sub-domain of your main site).
  • Access to your DNS provider's control panel.
  • Pro or Enterprise plan. Starter clubs use the default yourclub.freyaa.club subdomain.

Step 1: Set the custom domain in Freyaa

Open /dashboard/settings?tab=branding. The "Custom domain" panel asks for the full hostname (e.g., book.example.com). Save it.

We don't activate it yet — we wait for the DNS record to land. The status shows "Pending DNS" until then.

Step 2: Add the CNAME

In your DNS provider, add a CNAME record:

  • Host / Name: the sub-domain (e.g., book if your domain is example.com).
  • Type: CNAME
  • Value / Target: cname.freyaa.club
  • TTL: default (300 seconds is fine).

Some DNS providers (1&1, Hover) call CNAME "Alias". Same thing.

Step 3: Wait for SSL to provision

Our cron checks for the CNAME every 60 seconds. When it sees the record, it requests a Let's Encrypt certificate and serves your domain. Most clubs are live within 5 minutes of the DNS propagating; in rare cases (.uk domains with unusual registrars) it can take up to an hour.

Verifying it works

  • Open https://book.yourclub.com — you should land on your member portal with a valid SSL padlock.
  • The dashboard's "Custom domain" panel should show Active in green.
  • The default yourclub.freyaa.club still works as a fallback. We don't redirect — both addresses serve the same portal.

Removing or changing it

Click Remove in the panel. The custom domain is detached immediately; members fall back to yourclub.freyaa.club. You can leave the CNAME in your DNS provider — without us claiming the certificate it's harmless. To swap to a different domain, remove the old one first then add the new one.

Troubleshooting

  • "Pending DNS" forever. Use dig CNAME book.example.com or a free DNS-checker tool. If the record isn't propagating, the issue is at your DNS provider, not ours.
  • SSL error in the browser. Usually means the cert is still being issued — wait 5 more minutes. If still broken after an hour, email hello@freyaa.club.
  • Apex domain (no sub-domain). Most DNS providers don't allow CNAME on the apex. Use www.example.com or book.example.com, or move your DNS to a provider that supports ALIAS records (Cloudflare, Route 53).

Did this help?

If anything's missing or wrong, email us — we update articles when readers point things out.

Email feedback