Custom domain
Your website can live on your own domain — yourevent.com instead of the
nov3x.com address. Open the event → Website → Domain.
The flow is always the same three steps: connect, publish the DNS records, activate. Nothing goes live until you activate.
Plan: custom domains are an Aurora and above feature. Lower tiers see an upsell in place of the panel.
This panel and Settings → Custom Domains are two ways into one list. The workspace page is where domains live for the workspace as a whole; this panel binds one to a specific event’s website. The DNS records and the verification are the same either way.
1. Connect the domain
Enter the domain in Connect a domain. Enter the bare domain
(yourevent.com) — the www version is set up alongside it automatically.
Connecting only reserves the domain for this event. The domain shows as Not live and serves nothing yet.
The event needs a public address of its own before it can be activated. If you see “This event has no public address yet”, set the event’s slug on the website settings page first.
2. Publish the DNS records
Three records are needed. The panel lists each one with its host and value, a Copy button, and — after a check — whether it was Found or Not found:
| Record | Purpose |
|---|---|
| TXT | Proves you control the domain. Required for activation. |
| CNAME (apex) | Routes the domain to your website. |
CNAME (www) | Routes the www address too. |
Every record points at the same target — there is nothing per-domain to set up on the Novex side.
There are three ways to get these records published, in order of least work.
Publish automatically (recommended)
If the domain’s DNS is already on Novex’s Cloudflare and you have already confirmed you own the domain, use Publish records automatically. Nothing to copy, nothing to paste — and every later change to that domain is automatic too.
The confirmation is the part worth planning for: your ownership has to have been proved once already, by either of the two methods below. That first proof cannot be skipped, which is exactly what stops anyone pointing a domain they do not own at their own event.
If automatic publishing is not available you will see a message telling you so — either the domain’s DNS is not on our Cloudflare, or its ownership has not been confirmed yet. Use one of the two paths below, then try again.
Publish with your own Cloudflare token
If the domain’s DNS is on your Cloudflare account, Novex can publish the records with a scoped token you create:
- Click Open Cloudflare with these permissions pre-filled. This opens Cloudflare’s token form with Zone · DNS · Edit already selected.
- Under Zone Resources, include only the zone for this domain.
- Create the token and copy it.
- Paste it into Cloudflare API token and click Publish records.
If the button lands you on the plain API-tokens list instead of the pre-filled form, pick the “Edit zone DNS” template and follow the same steps — the permission you need is Zone · DNS · Edit and nothing else.
The token is used for that one request and then discarded. It is never stored, never logged, and never sent anywhere except Cloudflare.
If Cloudflare refuses, the panel says why: the token was rejected, no active zone was found for the domain on that token’s account, or the token cannot reach that zone (check the permission and that the zone is included).
Add the records by hand
If your DNS is somewhere else entirely, copy the three records from the panel into your DNS provider. This works everywhere and needs no credentials.
3. Verify, then activate
Click Verify DNS. DNS changes can take a few minutes to an hour to appear, so verify again if a record has not shown up yet.
Once the TXT record is visible, Activate. Visitors on your domain then see the website.
If the CNAME cannot be confirmed but the TXT can, you can still activate — the panel warns you and lets you through. A DNS provider that proxies or flattens CNAME records will legitimately hide it from a lookup. Activate and check the site.
Deactivate returns the event to its nov3x.com address only, keeping the
domain connected. Disconnect releases the domain entirely.
Related
- Publishing a website — making the public site live in the first place.
- Theme & identity — the branding visitors see when they arrive.