Connect your domain on AWS Route 53
Route 53 wants full record names and quoted TXT values — both differ from most panels.
AWS Route 53 wants the full record name
Paste the record name as shown, including .acme.com. In the dashboard, switch the Provider dropdown to full name so the Host column matches what this panel expects.
Where the DNS editor is
- AWS console → Route 53
- Hosted zones → your zone
- Create record
- Simple routing
Field names here: Record name for the record name, Value for the value, (inside the MX value) for MX priority.
The five records, as AWS Route 53 wants them
Your real values are on Domains in the dashboard — the verification token and the DKIM key are unique to your domain. Everything else looks exactly like this.
| Type | Record name | Value | What it does |
|---|---|---|---|
| TXT | _mailflat-verify.acme.com | mf-verify-… (yours is in the dashboard) | Proves you own the domain. Verification fails without it. |
| MX | acme.com | mail.mailflat.net.Priority 10 — (inside the MX value) | Routes incoming mail to MailFlat. |
| TXT | acme.com | v=spf1 include:mailflat.net ~all | Authorises MailFlat to send for your domain. |
| TXT | mail._domainkey.acme.com | v=DKIM1; k=rsa; p=… (yours is in the dashboard) | Signs your outgoing mail. |
| TXT | _dmarc.acme.com | v=DMARC1; p=none; | Tells receivers what to do when a check fails. |
Keep the trailing dot on the MX value
mail.mailflat.net. ends with a dot on purpose. AWS Route 53 treats a dotless target as relative and appends your domain to it, so mail is routed to a host that does not exist — with no error anywhere. Your domain can verify and still never receive a message.
AWS Route 53 specifics
Route 53 shows your zone next to the Record name box: leave it empty for the root, or type just _mailflat-verify. What it stores is the full name.
MX priority is part of the value here, not a separate field: enter 10 mail.mailflat.net. — trailing dot included.
Wrap TXT values in double quotes. Long DKIM keys must stay on one line.
Then verify
Back on Domains, press Verify. If it fails, the message says what is actually wrong — including the case where your records landed one level too deep, with the exact name we found them under. DNS changes are usually visible within minutes; a failure that names a wrong record will not fix itself by waiting.
More on custom domains: Custom domains (BYOD).