By default your attendees receive email from no-reply@adnab.co. If you would rather it came from your own address, such as tickets@events.yourcompany.com, you can set that up here. It takes one change to your domain's DNS. Nothing about how you run your events changes, and there is no data to move.
The setup itself takes a few minutes. The waiting is the slow part: DNS changes can take up to 48 hours to spread, so start this well before an event rather than the week of one.
What you need before you start
Someone who can add records to your domain's DNS. That is usually whoever manages your website, or your IT provider. You will also want to decide two things: the address emails should come from (tickets@ and events@ are common), and the display name attendees see in their inbox, which is normally just your organisation's name.
Enter your domain in Adnab
Go to Account, then Email Domain, and press Add domain. Enter the part before the @, the domain itself, and the display name. Save it and the domain appears in the list with five DNS records underneath, each with a copy button. There is an Export .txt button too, which is the easiest thing to forward to whoever manages your DNS. Nothing changes for your attendees at this point, and your existing emails keep arriving exactly as they do now. If you cannot see that tab, ask an owner or admin on your account, or email support@adnab.co.
Add the records to your DNS
All five are CNAME records, and each one has a copy button next to it so you do not have to retype anything. You may have set up email sending elsewhere and been given TXT records for SPF and DKIM: that is a different way of doing the same job, and you do not need them here. Add each record exactly as given, copying the host and value without changes. Most providers add your domain to the host automatically, so if you paste the full host and it ends up duplicated, remove your domain from what you pasted. Leave the TTL at whatever the provider suggests.
Why there are five and not three
Three of them prove the email really comes from you, which is what stops it being treated as forged. The other two cover the links inside your emails, so that anything an attendee clicks stays on your domain rather than showing an unfamiliar one. They arrive as two sets and both sets matter. Add all five together.
If you use Cloudflare, turn the proxy off for these records
Cloudflare shows a cloud icon next to each record. It must be grey, not orange. An orange cloud means Cloudflare is proxying the record, which changes what it resolves to and stops the check passing. This is by far the most common reason setup stalls, and it gives no error: the record looks correct in your dashboard while the check keeps failing.
Check the records
Back on the Email Domain tab, click your domain to show its records, then use the refresh action on that row to check them. Anything already resolving turns green, and anything still missing stays marked as waiting, so you can look at just those rather than starting again. DNS changes can take up to 48 hours to spread, so if you have only just added them and the check does not pass, it is usually worth waiting rather than changing anything. Check as often as you like; it costs nothing and changes nothing.
Choosing which domain sends
Once a domain verifies it is marked Ready, and the first one you verify starts sending straight away. If you run several brands you can add more than one domain and pick which one attendees hear from: use the send action on that row, and it changes to In use. Only one domain sends at a time, and only a verified domain can be chosen. Adding or verifying another domain never changes the one you are already using.
After it is verified
Once a domain is marked In use, your attendee emails start arriving from that address straight away, including for events that are already open and taking registrations. There is no cutover and nothing to schedule. Expect delivery to settle over the first week or two: a domain that has not sent email before has no reputation yet, so some inboxes are cautious at first. If you notice some messages landing in spam during this period, that is normal and resolves on its own as your domain builds a sending history. Sending normally is what fixes it, so carry on as usual and avoid sending anything unusually large in the first few days.
Where replies go
Replies go to the contact email address on your Adnab account, if you have set one. If you have not, they go to the address the email was sent from, so make sure that is a mailbox somebody actually reads. A reply address does not need any DNS setup of its own, so it can be on a completely different domain from the one you send from.
If you change DNS provider later
Move these records with everything else. If they go missing, your emails go back to arriving from Adnab's address, or stop, depending on your settings. Tell us at support@adnab.co before a migration and we can check the records again once it is done.
If something is not working
Your domain says Stopped working: it verified once and the records have since stopped resolving, so your emails have gone back to being sent by Adnab. Hover the warning for the detail. It usually means the records were removed or the domain moved provider. Records added but the check keeps failing: check the Cloudflare proxy first, then give it up to 48 hours before changing anything. If your provider added your domain to the host automatically, look for a doubled-up host like em1.events.yourcompany.com.events.yourcompany.com. Emails going to spam soon after verification: normal for a new domain, and it settles. If it is still happening after a few weeks, email us. Lost access to the domain, or it has been transferred away: tell us as soon as you can, at support@adnab.co, and we will move you back to sending from Adnab's address so your attendees keep receiving their tickets.