FFree Domain MailFREE
Sign inCreate accountOpen app →
Open menu

Blog

How to Add MX and TXT Records in Amazon Route 53

By Free Domain Mail team · Operated by Hoang Uy Household Business · Updated

Route 53 stores records in a hosted zone, and two of its rules trip people up: the MX priority is typed inside the value, and TXT values must be wrapped in double quotes. To receive mail at every address on a domain with Free Domain Mail, add one TXT ownership record and one MX record for mx.freedomainmail.com.

A real DNS records table showing record name, type and value fields
Real DNS editor example with private record values blurred. Field labels vary by provider. Compare with the provider's official instructions.

Step-by-step setup

  1. 1Open the Route 53 console, choose Hosted zones, then the zone for the domain.
  2. 2Confirm the registrar uses the four name servers listed in the zone's NS record.
  3. 3Choose Create record, Simple routing. Record name _maildock-verify, type TXT, value "maildock-verify=…" in double quotes.
  4. 4Create or edit the root MX record: Record name empty, type MX, value 10 mx.freedomainmail.com as the only line.
  5. 5Wait for the TTL, then run DNS Checker below; once both records pass, every address at the domain receives mail.

What goes in each DNS field

TypeName / HostValue / DataPriority
MX(empty)10 mx.freedomainmail.cominside the value
TXT_maildock-verify"maildock-verify=…" (shown in the app, in double quotes)—

Interface reference: AWS Route 53 — Working with records. Always copy the domain-specific values shown inside your Free Domain Mail setup.

The two records for a catch-all inbox

Free Domain Mail turns a domain you own into a catch-all inbox: every address at the domain receives mail, and there are no mailboxes to create. Messages are kept for 90 days and never forwarded; sending from the domain is optional and needs three more TXT records shown in the app.

You add two records: a TXT record at _maildock-verify that proves you own the domain, with the maildock-verify=… value shown in the app (it is unique to your domain, so copy it exactly), and an MX record for the root of the domain that points to mx.freedomainmail.com with priority 10.

DNS records to add (copy the exact TXT value shown in the app)
Type  Name / Host        Value                                  Priority
TXT   _maildock-verify   "maildock-verify=…" (in quotes)      —
MX    (empty)            10 mx.freedomainmail.com               (in value)

Create the records in the hosted zone

In the Route 53 console open Hosted zones, choose the zone for the domain, then Create record and keep Simple routing.

For the TXT record type _maildock-verify in front of the domain name in Record name, choose type TXT and enter the value in double quotes, for example "maildock-verify=…" with the value from the app. A TXT string can be at most 255 characters per quoted part.

For the MX record leave Record name empty, which is the root of the domain, choose type MX and enter 10 mx.freedomainmail.com as the value: priority, a space, then the mail server. A TTL of 300 seconds makes later changes quicker.

Replace an existing MX record

Route 53 keeps all MX values for a name in one record with one value per line. If the root already has an MX record, edit it and replace its values with the single line 10 mx.freedomainmail.com, so no old mail server is left in the set.

If the domain already receives mail you depend on, such as Amazon WorkMail or Google Workspace, connect a different domain or a subdomain instead.

The registrar must use this zone's name servers

Records in a hosted zone only answer queries when the domain's registrar lists the four Route 53 name servers of that zone. Leave the NS and SOA records that Route 53 created untouched. If the domain is registered elsewhere and uses other name servers, add the records there instead.

SPF, DKIM and DMARC: only if this domain also sends mail

Receiving at the catch-all inbox does not need SPF, DKIM or DMARC. These records are only needed if this domain also sends mail: through Free Domain Mail, add the three TXT records shown on the domain page (DKIM at fdm1._domainkey, an SPF include for _spf.freedomainmail.com and DMARC); through another provider, use that provider's values.

In that case keep one SPF TXT record at the root and merge every sending service into it rather than adding a second v=spf1 record. Copy DKIM selectors exactly as that provider shows them, and publish DMARC as a TXT record at _dmarc, starting with p=none.

Check the result

Wait for the old TTL to pass, then run an MX lookup from outside AWS. The answer should list only mx.freedomainmail.com.

Send a message from an outside account to any name at the domain, even one you have never used. If it arrives in the inbox, the catch-all is working.

Common errors with Amazon Route 53

Priority in a separate field

Route 53 has no Priority field: an MX value contains the priority and the host together, as 10 mx.freedomainmail.com.

TXT value without double quotes, or a second TXT record set

Route 53 TXT values are strings in double quotes, for example "maildock-verify=…". With simple routing, all TXT values for one name live in the same record: if the name already has a TXT record, add the new value on its own line in that record instead of creating another one.

Editing the wrong hosted zone

Only the hosted zone whose four name servers are set at the registrar answers for the domain. If you created a second hosted zone with the same name, records added there are never seen. Compare the zone's NS record with the name servers on the registered domain.

How long DNS takes at Amazon Route 53

AWS says changes generally propagate to all Route 53 name servers within 60 seconds. After that, resolvers that cached the old answer keep it until the record's TTL runs out, so a low TTL on the old MX record shortens the wait.

Sources, checked on November 8, 2026:

Common mistakes to avoid

  • Entering the priority in a separate place instead of inside the MX value.
  • Leaving the TXT value without double quotes.
  • Typing @ as the record name; Route 53 uses an empty name for the root.
  • Creating the records in a hosted zone the registrar does not point to.

Frequently asked questions

What is the MX value format?

Priority, a space and the server: 10 mx.freedomainmail.com. A trailing dot is optional.

Why are quotes needed for TXT?

Route 53 expects each TXT string in double quotes; it splits long values into several quoted strings of up to 255 characters.

Can I use a subdomain?

Yes. Use the subdomain as the record name, for example qa, and mail for the main domain is not affected.

Do I need to create each email address?

No. Once the TXT and MX records are verified, every address at the domain receives mail.

Technical references

Primary specifications and provider documentation relevant to this guide:

Useful next steps

Related guides