Set up Ayamail on a 123 Reg domain
A lot of small UK businesses, clubs and families registered their .co.uk or .uk name with 123 Reg years ago and never touched the settings again. This guide shows how to send the mail for that name to Ayamail while the domain itself stays at 123 Reg.
Written by Ayamail editorial team · Updated 30 October 2026
Short answer
In short: log in to the 123 Reg Control Panel, click Manage All next to Domains, pick your domain and choose DNS. Remove the old MX records, use Add New Record to create an MX record for mx1.ayamail.net. with priority 10, then add the TXT records shown in Ayamail.
Have these ready
Changing the records at 123 Reg
123 Reg has redesigned its Control Panel. Older help articles on other sites mention Manage DNS and an Advanced DNS tab; today the same records sit on a screen simply called DNS.
Find the DNS screen
Log in to the 123 Reg Control Panel. In All Products and Services, click Manage All next to Domains, select your domain and choose DNS in the navigation bar.
Delete the 123 Reg mail records
If you had 123 Reg email, you will see MX records with values such as smtp.secureserver.net. and mailstore1.secureserver.net. Delete them. Leaving them in place means some mail would still go to the old mailbox.
Create the MX record
Click Add New Record. Set Name to @, Type to MX, Priority to 10 and Value to mx1.ayamail.net. with the full stop at the end. 123 Reg's own guide stresses that MX values must end with a full stop or they will not work.
Add the TXT records
Click Add New Record again for each TXT record: SPF on @, the ownership code on _ayamail, DMARC on _dmarc and the DKIM key on dkim._domainkey. Paste the values from Ayamail exactly, without extra spaces or quotation marks.
Add the optional CNAME records
autoconfig, autodiscover and mail can point to mx1.ayamail.net. They help mail apps fill in the server settings themselves. Mail works without them.
Give it time, then check in Ayamail
123 Reg warns that DNS changes can take 24 to 48 hours to be visible everywhere, though it is often quicker. Run the check on the Domains page in Ayamail and fix any record that stays red.
Records to create
Copy the ownership code and DKIM key from Ayamail. They are different for every domain.
| Setting | Value |
|---|---|
| Mail server (MX) | mx1.ayamail.net |
| Priority | 10 |
| Setting | Value |
|---|---|
| MX value as 123 Reg wants it | mx1.ayamail.net. |
| SPF (TXT, name @) | v=spf1 mx a:mx1.ayamail.net ~all |
| Ownership (TXT, name _ayamail) | ayamail-verify=… copied from Ayamail |
| DMARC (TXT, name _dmarc) | v=DMARC1; p=quarantine; … copied from Ayamail |
| DKIM (TXT, name dkim._domainkey) | v=DKIM1; k=rsa; p=… copied from Ayamail |
Already have an SPF record for 123 Reg's mail? Replace it with the one above rather than keeping two SPF records.
Your old 123 Reg mailbox and website
Changing the MX record does not delete the 123 Reg mailbox, but new mail stops arriving there. Use the import in Ayamail to fetch the old messages over IMAP before you cancel the email package, then cancel it so you do not keep paying for a mailbox nobody reads.
Your website is not affected. Its A and CNAME records for www are separate from the mail records, so a site hosted at 123 Reg or elsewhere keeps running. Only touch the records listed on this page.
If you would rather not deal with two companies, you can also move the domain itself to Ayamail later. That needs a paid plan and the transfer code from 123 Reg. There is no need to do it to use Ayamail mail.
Common problems
The MX record is saved but Ayamail says it is wrong
What to do: Check the trailing full stop on the value. Without it, some panels add your domain name to the end, so the record points to mx1.ayamail.net.yourdomain.co.uk.
Nothing you change seems to matter
What to do: The domain probably uses other nameservers. Check them in the 123 Reg Control Panel; if they belong to a web host or Cloudflare, add the records there.
Some mail still appears in the old webmail
What to do: An old secureserver.net MX record is still there, or other servers have the old one cached. Delete leftovers and wait a day.
Questions and answers
- Will my .co.uk domain stay registered with 123 Reg?
- Yes. You only change where its mail is delivered. Renewal and billing for the domain stay with 123 Reg.
- Why does the MX value need a full stop at the end?
- It marks the name as complete. 123 Reg's help says MX values must end with one, otherwise the record will not work.
- Can I use a domain from 123 Reg for a family?
- Yes. Once the domain is verified you can create aliases on it that forward to your Ayamail mailboxes. The pricing page shows how many people each plan includes.
- Do I need the autoconfig records?
- No. They make setting up mail apps easier, but mail is delivered without them.
Sources
- 123 Reg: How do I set up an MX record on my domain name? (Checked 30 October 2026)
Related guides
- Namecheap
Point a Namecheap domain at Ayamail: choose Custom MX under Mail Settings in Advanced DNS, add the TXT records and check nothing else catches your mail.
- Gandi
Connect a Gandi domain to Ayamail: swap the default Gandi Mail MX pair on the DNS Records tab, add the TXT records and bring your old mail with you.
- Domain with email
Search, buy or transfer a domain in Ayamail and get working mail on it without touching DNS. Mail records are set up for you, and you can leave any time.
- Email for freelancers
Your own domain, role addresses like invoices@ and hello@ in one inbox, no ads and servers in Germany. Email for sole traders and freelancers.