eusend
DomainsDNS Providers

Amazon Route 53

Publish your eusend DNS records in Route 53 — quoting and splitting the DKIM value, the MX priority format, and the duplicate hosted zone that quietly breaks everything.

Route 53 is stricter than every other panel in this list about how a TXT value is written. It will not split your DKIM key for you, and it will not add the quotes.

Split the DKIM value first

A single DNS string holds 255 characters; your DKIM value is around 400. Route 53 requires you to break it into pieces yourself, wrap each in double quotes, and put them on one line separated by spaces. Its own limit is 4,000 characters in total, so two pieces is always enough.

Paste your value into this to get the exact string Route 53 wants:

split the DKIM value
echo -n 'v=DKIM1; k=rsa; p=MIIBIjANBgkq…' | fold -w 255 | sed 's/.*/"&"/' | tr '\n' ' '

The result looks like this, and goes into the value box as-is:

"v=DKIM1; k=rsa; p=MIIBIjANBgkq…" "…rest of the key…"

Never shorten the key to fit. Splitting changes nothing about the record — a resolver joins the strings back together — but a truncated key breaks DKIM.

Add the records

Open the hosted zone

In the Route 53 console, choose Hosted zones in the navigation pane, then the name of your zone. Choose Create record. If the console asks for a routing policy, choose Simple routing.

DKIM — required

FieldValue
Record nameeusend._domainkey
Record typeTXT
Valuethe quoted, split value from above
TTL300

The Record name box shows .acme.com beside it — that suffix is added for you, so type only eusend._domainkey.

FieldValue
Record name_dmarc
Record typeTXT
Value"v=DMARC1; p=none; rua=mailto:dmarc@acme.com"

Short enough for one string, but the quotes are still required. Use an address you actually read for rua — see DMARC.

Return-Path — optional, both or neither

FieldValue
Record namesend
Record typeTXT
Value"v=spf1 include:_spf.eusend.dev ~all"

Then a second record. Route 53 has no separate priority field — the priority and the mail server go in one value, separated by a space:

FieldValue
Record namesend
Record typeMX
Value10 feedback.eusend.dev

Publish both and eusend switches your mail to a bounce address on your own domain, so SPF passes and aligns. One without the other does nothing.

Route 53 specifics

Everything in a TXT value is quoted. Route 53 rejects unquoted values, and a value that saved without quotes is not the value you think it is. This applies to the short records too.

To enter two separate TXT records at the same name, put each value on its own line in the same record — not in two records. Route 53 treats one name plus one type as a single record with multiple values.

The zone apex has an empty name. Not @. AWS is explicit: "If you're creating a record that has the same name as the hosted zone, don't enter a value (for example, an @ symbol) in the Name field." None of the eusend records sit at the apex, so this only comes up if you publish DMARC there.

Check you are editing the live hosted zone. Route 53 lets you keep several hosted zones for the same domain name, each with its own nameservers, and only one of them is authoritative. Records added to the wrong one are invisible to the internet and to us. Compare the NS values in the zone against dig +short NS acme.com before you start — this is the single most common reason a correct-looking Route 53 record never verifies.

Registered elsewhere? If the domain is registered outside AWS, its nameservers at that registrar must point at this hosted zone's four NS values. Creating the zone does not do that for you.

Check it

verify
dig +short TXT eusend._domainkey.acme.com

Route 53 propagates to its own nameservers within about 60 seconds of saving.

Official documentation: Creating records by using the console and TXT record type.