Set up the DNS records
Add the DNS records OmniLab sends for your subdomain, then hand back so OmniLab can finish the setup.
This is a job for whoever manages your DNS, often IT rather than marketing.
Before you begin
- Agree the exact subdomain with your Customer Success Manager, for example
play.lindenhall.example. - Find out who can edit DNS for the domain, and how long approval takes. Approval, not the change itself, is what delays launches.
Add the records
Your Customer Success Manager emails the records to add. There are usually two:
| Record | Type | Name | Value |
|---|---|---|---|
| Certificate validation | CNAME | As sent | As sent |
| Website routing | CNAME | Your subdomain, for example play | Your default address, for example lindenhall.topage.co |
If your subdomain is already covered by OmniLab's certificate, the email only has the routing record.
- If a record already exists at the routing name, lower its TTL to 300–600 seconds.
- Wait for the old TTL to expire, so a rollback takes minutes rather than a day.
- Create each record exactly as sent.
- Tell your Customer Success Manager the records are in place.
Keep the certificate validation record after launch. It renews the certificate automatically, and deleting it breaks the address when the certificate expires.
Use a subdomain, not your root domain. Most DNS providers can't host a CNAME at the root, and you don't want your main website pointing at OmniLab.
Wait for OmniLab to finish
OmniLab checks the records, completes the configuration and runs a final validation, then confirms the address is live. Records can take from minutes to 48 hours to appear everywhere, depending on your provider and the previous TTL.
Test the address
- Open a published campaign on the new address, in a normal browser.
- Check the padlock shows, with no certificate warning.
- Play the full journey through to a reward.
If something's blocked
- OmniLab says it can't see the records: check them with a public DNS lookup tool. Your own browser and network may show an old result.
- A certificate warning on the new address: the validation record is missing or mistyped. Compare it with the email, character by character.
- The address works for you but not for a colleague: their network still holds the old value. Wait out the original TTL.
- Your provider won't accept a CNAME at that name: some providers refuse a CNAME where other records already exist at the same name. Use another subdomain, or ask your provider for their equivalent record type.