Is Route 53 your DNS host?
Yes, if the domain's nameservers read ns-….awsdns-….com, .net, .org and .co.uk: four of them, one on each. Then the records go in a hosted zone in the AWS console.
A domain registered through Route 53 gets a hosted zone and those nameservers automatically. A domain registered elsewhere uses Route 53 only if its registrar was pointed at them. If the nameservers name another company, that host's guide is the one to follow.
Check you are in the right zone
An AWS account can hold more than one hosted zone with the same name, and only one of them is the zone the world asks. It happens when a zone is deleted and made again, or made twice by accident, and each zone has its own four nameservers. No other host has this trap. Before you add anything:
- Open the zone and choose View details (or look at Hosted zone details).
- Check its Name servers are the four the domain actually uses. They are under Registered domains if you bought the domain through AWS, and at your registrar otherwise.
- Check its Type reads Public. A private hosted zone answers only inside an AWS network, so nothing outside it, no sender and not imado, can see its records.
Records added to the other zone are saved and listed, and never answered. Nobody sending you mail ever sees them.
Where the records go
- Sign in to the AWS console and open Route 53.
- Choose Hosted zones, then the zone's name.
- Press Create record. The console opens either the quick form or a wizard; if it is the wizard, choose Switch to quick create. The fields below are the quick form's.
- Fill in the fields and press Create records.
What Route 53 calls each field
Two of Route 53's fields hold something different from most other hosts:
- A TXT value is typed inside double quotes.
- The MX record's priority is part of its value, not a field of its own.
The table under Add the six records shows both, already written the way Route 53 wants them.
- Record type · Type on imado
- Choose it from the list: TXT, CNAME or MX.
- Record name · Host on imado
- Only the part before your domain — Route 53 shows .example.com after the field and adds it itself. For the MX record, leave it empty: Route 53 takes @ as an ordinary character, so @ makes a record for @.example.com.
- Value · Value on imado
- A TXT value goes inside double quotes, and the MX value starts with its priority — 10, a space, then the server. imado's page writes them that way once it recognises Route 53; copy them as they are, adding nothing.
- (in Value) · Priority on imado
- Route 53 has no Priority field. It is the number at the front of the MX record's Value.
- TTL (seconds)
- Leave it at the default Route 53 fills in.
- Routing policy
- Leave it at Simple routing.
- Alias
- Leave it off. It is for pointing at AWS resources, and turning it on replaces the Value box with a picker.
What to put for the domain itself
One record, the MX record that makes mail arrive, belongs to the domain itself rather than to anything in front of it. Every DNS panel has its own way of saying that, and on Route 53 the usual answer is the one that breaks.
Leave Record name empty for the MX record. Not @, and not example.com. Route 53 saves @ as a real name, @.example.com, without a warning and with a correct-looking value, and mail to your domain never reaches imado.
AWS's own documentation says it plainly: for a record with the same name as the hosted zone, do not enter a value. @ is the convention most other panels use, so instructions written for one of them will tell you to type it. Typing example.com is no better: Route 53 already shows .example.com after the field.
The other five records all have something in front of the domain: _imado-challenge, _dmarc and the three _domainkey names. Those go in Record name exactly as shown, with nothing after them.
Add the six records
First the ownership record; then, once imado shows it as Added, the other five. Each is a Create record with Routing policy left at Simple routing and Alias off.
- TXT
- Record name
- _imado-challenge
- Value
- "imado-verification=…"
- CNAME
- Record name
- ….
_domainkey - Value
- ….
dkim. amazonses. com
- CNAME
- Record name
- ….
_domainkey - Value
- ….
dkim. amazonses. com
- CNAME
- Record name
- ….
_domainkey - Value
- ….
dkim. amazonses. com
- MX
- Record name
- (empty)
- Value
- 10 inbound-smtp.
us-east-1. amazonaws. com
- TXT
- Record name
- _dmarc
- Value
- "v=DMARC1; p=none;"
| Record type | Record name | Value |
|---|---|---|
| TXT | _imado-challenge | "imado-verification=…" |
| CNAME | …. | …. |
| CNAME | …. | …. |
| CNAME | …. | …. |
| MX | (empty) | 10 inbound-smtp. |
| TXT | _dmarc | "v=DMARC1; p=none;" |
When imado sees that your domain is served by Route 53, your domain's page already shows every value this way, quoted and with the priority in front. Copy it with the button and paste it as it is, adding nothing.
If the page instead offers a choice of forms, it has not recognised Route 53. Pick the one with the priority included, and put the quotes around the two TXT values yourself. Route 53 treats a trailing dot on the MX and CNAME values as optional, so either form is fine.
What gets in the way
An MX record already on the domain
Route 53 keeps exactly one record per name and type. If the zone already has an MX record, from WorkMail, Google Workspace or an earlier SES setup, Create record refuses a second one as already existing. Select the existing MX record, choose Edit record, and replace its value with imado's.
Replace the old value; do not add imado's beside it. Several lines in one MX record are several mail servers, and the old one would keep receiving some of the mail.
A DMARC record already on the domain
The same rule applies to _dmarc: edit the existing TXT record there rather than adding one. A domain may publish only one DMARC policy, so keep yours if you already have one you meant to set.
Records that look right but are not seen
Check the zone's name servers against the domain's, as in Check you are in the right zone. The wrong hosted zone is the most common reason a correct Route 53 record is invisible.
Checking too early
A name looked up before its record existed can be remembered as missing for up to a quarter of an hour. Add the record first, then press Check again.
Then, on imado
Back on your domain's page, press Check again. Route 53 publishes a change to all of its nameservers within a minute.
When the ownership record is Added, the other records appear. When those are, create the mailbox and send yourself a message: steps 5 and 6 of the setup.
AWS's own guides cover creating a record, the value each field takes, and how TXT and MX values are written.