Connect your own domain: DNS records step by step
You own a domain such as yourname.co.uk and want your mail to arrive in Ayamail. This page lists every DNS record the Ayamail app asks for, explains what each one does and shows the order that causes the least disruption. The exact values for your domain always appear in the app, ready to copy.
Written by Ayamail editorial team · Updated 30 October 2026
Short answer
Add your domain under Domains in Ayamail, then create five records where your domain's DNS is managed: an ownership TXT record, one MX record, one SPF record, a DKIM key and a DMARC policy. Remove old MX and SPF records from your previous provider. The app checks the records and tells you when mail is ready.
Before you change anything
Choose how to connect
On the Setup tab the app offers the routes that work for your domain and preselects the easiest one.
Ayamail nameservers
You point the domain's nameservers to Ayamail, and we keep the mail records up to date. This works for any domain whose registrar allows a nameserver change. The switch is automatic only for domains bought through Ayamail. Afterwards every record, including the ones for your website, is managed under Domains in Ayamail, so recreate any website records there before you switch.
Approve at your DNS provider
For some DNS providers the app can send the records for you to approve at the provider. It is offered only when the app has confirmed it works for your domain, so you may not see it.
Manual setup
You create each record yourself at your DNS provider. This always works and is what the registrar guides below describe.
The records Ayamail asks for
The app shows these on the DNS records tab with the values for your domain. The name is the part in front of your domain; @ means the domain itself.
- Ownership: TXT record on _ayamail with the value ayamail-verify= followed by a code that is unique to your domain. It proves the domain is yours.
- Receiving: MX record on @ pointing to the mail server in the table below, with the priority shown there.
- SPF: TXT record on @ with the value v=spf1 mx a:mx1.ayamail.net ~all. A domain may only have one SPF record.
- DKIM: TXT record on dkim._domainkey with a value that starts v=DKIM1; k=rsa; p= followed by your domain's public key. It appears a few minutes after you add the domain.
- DMARC: TXT record on _dmarc with the value v=DMARC1; p=quarantine; rua=mailto:dmarc@ayamail.net; ruf=mailto:dmarc@ayamail.net; fo=1; adkim=r; aspf=r; pct=100
MX record
| Setting | Value |
|---|---|
| Mail server (MX) | mx1.ayamail.net |
| Priority | 10 |
Ayamail uses a single MX record. Delete MX records that point to other mail servers.
Optional records
Behind Show optional records on the DNS records tab you find records that make life easier but are not needed for mail to flow:
- CNAME autoconfig, autodiscover and mail pointing to mx1.ayamail.net. Mail apps such as Thunderbird and Outlook use them to find the server settings on their own.
- CNAME mta-sts pointing to mta-sts.ayamail.net and a TXT record on _mta-sts with the value from the app. Together they ask other mail servers to always use a secure connection to you.
- TXT on _smtp._tls with v=TLSRPTv1; rua=mailto:tlsrpt@ayamail.net, so that connection problems are reported.
When the app reports a problem
More than one MX record
What to do: An old MX from your previous provider is still there, so some mail would go there. Delete it. The app treats this as blocking.
Two SPF records
What to do: Receivers reject a domain with two TXT records that start v=spf1. Delete the old one, or replace its value with Ayamail's if you no longer send through the old provider.
A CNAME is in the way
What to do: A name that has a CNAME cannot hold any other record. Some providers put a CNAME on _dmarc. Delete it before you add the DMARC TXT record.
The records are correct but still shown as pending
What to do: DNS changes can take up to 24 hours to show everywhere. Press Check now later; the app also keeps checking on its own.
What does an MX record actually do?
Priority, fallbacks and common mistakes, explained without the jargon.
Step by step at your registrar
Cloudflare, GoDaddy, IONOS, OVHcloud, one.com, Simply.com and Squarespace each have their own quirks.
Questions and answers
- Will my website stop working?
- No, not with manual setup. You only change mail records, so A, AAAA and www records stay as they are. If you switch nameservers to Ayamail, recreate the website records in Ayamail first.
- What happens to mail in my old mailboxes?
- It stays with the old provider until you move it. New mail goes to Ayamail as soon as the MX record has spread. Import the old mail before you cancel anything.
- Why does the DKIM record say it is not ready?
- The signing key is created when you add the domain and usually takes a few minutes. Until then the app does not ask you to create the DKIM record.
- Can I keep sending through another service, such as a newsletter tool?
- Yes, but there may only be one SPF record. Add the other service's include to Ayamail's SPF value instead of creating a second record.
- Do I have to buy the domain from Ayamail?
- No. You can connect a domain from any registrar. You can also buy one through Ayamail, in which case the setup is done for you.
Related guides
- 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.
- 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.
- GoDaddy
Add Ayamail's MX and TXT records at GoDaddy. When GoDaddy's DNS applies, and what to do first if the domain has Microsoft 365 from GoDaddy.
- one.com
Point a domain hosted at one.com to Ayamail. Where the DNS records are, why the hostname stays empty and what happens to your one.com mailboxes.