Connecting your own domain

Your public event website is hosted by iveo. To make it reachable under your address — say programme.example.org — two records are needed in the DNS zone you control. Your domain then stays in the address bar throughout; no third-party branding appears there.

This page is written for whoever looks after your DNS. No iveo account is needed for it.

What we need from you first

1. The exact hostname you want to use. A subdomain is recommended — see the note on apex domains below.
2. Who manages your DNS — registrar, Cloudflare, IONOS, Squarespace or something else — and confirmation that your IT can create records there.

The two records

Once the domain is registered in iveo, the concrete values appear in the event settings. Take them from there — the placeholders below only show the shape.

#	Type	Name / host	Value	Purpose
1	CNAME	your hostname	the iveo edge host	Routes visitors to the event website
2	TXT	_iveo-domain-verify. + your hostname	your verification token	Proves you own the domain

No record is needed for the TLS certificate. iveo issues it automatically once ownership is confirmed.

What to watch out for

• Apex domains (example.org with no subdomain) cannot carry a CNAME. Use a subdomain — or your provider’s ALIAS or ANAME record type if it offers one.
• Cloudflare: the CNAME must be DNS-only — grey cloud, not orange. Proxying breaks the automatic certificate issuance.
• Enter the TXT value without surrounding quotes; most control panels add them by themselves.
• TTL 300 seconds during setup — that keeps corrections fast.
• Do not delete unrelated records. Your existing website, www, MX records for mail: all of it stays. You are only adding the two rows above.

Once the records are in place

DNS changes typically take 5 to 60 minutes, occasionally longer. During that time iveo checks the TXT record automatically and then issues the certificate. In the event settings the status switches to “TLS active” once everything is in order.

Until then the address may show a notice that the domain is not active yet. That resolves by itself once propagation completes. After that the website is reachable under your address, sub-pages included.

If something goes wrong

Symptom	Likely cause	What helps
“Domain not yet active”	The TXT record is not being found yet	Check record 2 exactly, then wait for propagation
Certificate “being issued”	Issuance still in progress	Wait 10–30 minutes; if it stays on a TLS error, get in touch
Site does not load at all	CNAME missing or pointing at the wrong target	Check record 1 and copy the target value from the iveo settings
www works but the hostname does not (or the reverse)	Record created on the wrong host label	Create it on exactly the agreed hostname
Cloudflare: TLS never validates	The record is proxied (orange cloud)	Switch it to DNS-only (grey cloud)

Changing or removing it later

If you no longer want to use your own domain, remove it in the event settings; you can then delete the DNS records. To move to a different hostname, repeat the steps above with the new name.

If your domain already runs through an older arrangement, such as an NS delegation, that continues to work. For new setups we recommend the route above.