Your OVHcloud domain with Ayamail mail
OVHcloud is a large European host, and plenty of domains keep their DNS zone there together with MX Plan or a hosting plan that includes mailboxes. To receive that mail in Ayamail you edit the DNS zone in the OVHcloud Control Panel. Two OVHcloud details make all the difference: the five MX records to remove and the dot at the end of hostnames.
Written by Ayamail editorial team · Updated 30 October 2026
Short answer
In the Control Panel go to Web Cloud, Domain names, pick the domain and open the DNS zone tab. Delete the MX records for mx0 to mx4.mail.ovh.net and OVHcloud's SPF, then use Add an entry for the MX and TXT records from the Ayamail app. End the MX target with a dot. Allow 4 to 24 hours.
The five OVHcloud MX records to remove
For MX Plan, Email Pro, Exchange and Zimbra, OVHcloud publishes five MX records: mx0.mail.ovh.net with priority 1, mx1 with 5, mx2 with 50, mx3 with 100 and mx4 with 200. Adding Ayamail's with a better priority is not enough: whenever Ayamail's server was briefly unreachable, senders would deliver to OVHcloud instead. The Ayamail app reports any extra MX as blocking. Filter the table by MX and delete all five.
OVHcloud's SPF, v=spf1 include:mx.ovh.com ~all, also has to make way for Ayamail's. If an OVHcloud hosting plan still sends mail, such as notifications from a website, add include:mx.ovh.com to Ayamail's value instead of keeping two SPF records.
Edit the DNS zone step by step
Back up and import
MX Plan mailboxes receive nothing once you switch. Import their content into Ayamail first, using the option for another IMAP server and the incoming server OVHcloud lists.
Open the zone
Web Cloud, Domain names, your domain, DNS zone tab. The domain must use OVHcloud's DNS servers; otherwise edit the zone at whichever DNS host you chose.
Delete the old ones
For every OVHcloud MX and the old SPF, open the ⋮ menu on the row and delete the entry. You can also tick several rows and use the delete button above the table.
Add the MX
Click Add an entry and choose MX. Leave the sub-domain empty, enter the priority from the table and the target mx1.ayamail.net. ending with a dot. TTL By default is fine. Click Add.
Add the TXT records
Again with Add an entry, type TXT: sub-domain _ayamail, empty for SPF, _dmarc and dkim._domainkey, each with its value copied from the app. Then press Check now in Ayamail.
MX priority and target
| Setting | Value |
|---|---|
| Mail server (MX) | mx1.ayamail.net |
| Priority | 10 |
At OVHcloud, end the target with a dot so your domain is not added to it.
Redirections, a safety net and timing
Email redirections and MX Plan mailboxes run on OVHcloud's mail servers. Once the MX points to Ayamail, mail no longer passes through them, so a redirection set up at OVHcloud stops working. Recreate it in Ayamail as an alias or forward.
Before you change anything, note that the zone's actions menu can show the DNS zone history, where you can view, download or restore an earlier version. The same menu lets you change the default TTL; lowering it the day before speeds up the switch. A text mode exists too, but OVHcloud keeps it for experienced users because one syntax error can break the whole zone.
OVHcloud quotes 4 to 24 hours for an MX change to propagate fully.
If something goes wrong
The MX becomes mx1.ayamail.net.yourdomain.co.uk
What to do: The target was entered without a final dot. Edit the entry and add the dot after net.
Mail still arrives in MX Plan
What to do: One of mx0 to mx4.mail.ovh.net is still there, or the old TTL has not expired. Filter the table by MX.
An error after editing in text mode
What to do: Restore the previous version from the zone history, then make the changes with Add an entry instead.
What each record is for
The full list with SPF, DKIM and DMARC values and the optional records.
Questions and answers
- Is my website hosted at OVHcloud affected?
- No. A, AAAA and www records stay as they are. Only the destination of your mail changes.
- Should I cancel MX Plan?
- Only after importing and checking your mail in Ayamail. An MX Plan included with hosting can simply stay unused.
- Why does the final dot matter?
- OVHcloud completes a target without a final dot with your own domain. The dot says the name is already complete.
- Can I use the Ayamail nameservers instead?
- Yes, if you change the domain's DNS servers at OVHcloud. Recreate your website records in Ayamail first.
Sources
- OVHcloud: Edit a DNS zone (Checked 30 October 2026)
- OVHcloud: Configure an MX record for email management (Checked 30 October 2026)
- OVHcloud: Improve email security with an SPF record (Checked 30 October 2026)
Related guides
- Connect your domain
Which MX, SPF, DKIM and DMARC records to add, where to add them and how to check they work. With guides for Cloudflare, GoDaddy, IONOS and more.
- MX records explained
What an MX record does, how priority works, how to look one up on Windows, Mac and Linux, and the mistakes that make mail go missing.
- 123 Reg
Move the mail for a .co.uk or .uk domain at 123 Reg to Ayamail: where the DNS screen is, the full stop MX values need and which old records to delete.
- Cloudflare
Add Ayamail's MX, SPF, DKIM and DMARC records in Cloudflare. Why the CNAMEs must be DNS only and how to switch off Email Routing safely.