DNS host
Amazon Route 53 SPF, DKIM and DMARC records
In Route 53 open Hosted zones, choose the domain and select Create record. SPF is a TXT record with Record name left blank, DMARC a TXT record at _dmarc, and DKIM a CNAME or TXT at <selector>._domainkey. Put TXT values in double quotes and split a key over 255 characters into quoted strings on one line. Use TXT for SPF: AWS no longer recommends the SPF type.
Amazon Route 53
What goes in Record name
- SPF · Record name
Leave blank (the domain itself)
- DKIM · Record name
<selector>._domainkey- DMARC · Record name
_dmarc
Check the records after you save them
Enter the domain: SPF, DKIM at common selectors, DMARC and MX are looked up live, so you see whether Amazon Route 53 is serving the new records yet.
Try
Lookups go from your browser to Cloudflare's public DNS resolver; nothing is stored. Without a selector the checker tries the ones providers document.
What you get
The result, in plain words
- Pass, warning or fail for SPF, DKIM, DMARC and MX
- SPF lookups counted against the limit of 10
- DKIM keys found at google, selector1, selector2 and 50+ other selectors
- The records to publish, with the steps at your DNS host
Amazon SES
Amazon SES writes its records into Route 53
When the hosted zone is in the AWS account you send from, SES can publish its DKIM and custom MAIL FROM records to Route 53 itself; the records are on our Amazon SES page. Sending through another provider? Skip to the field values.
Amazon SES
Domains whose Route 53 hosted zone is in the same AWS account as SES
- At creation
Publish DNS records to Route53: Enabled
- Later
Identity > Authentication tab > Publish DNS records to Route53
- What it adds
The three Easy DKIM CNAMEs, plus the MX and TXT records of a custom MAIL FROM subdomain
- The custom MAIL FROM subdomain takes exactly one MX record; with more than one, the setup failssource (opens the vendor's page in a new tab)
- The Publish DNS records to Route53 button shows only while the records are unpublished; after the click SES shows a confirmation banner and the button goes awaysource (opens the vendor's page in a new tab)
Step by step
Create the identitysource (opens the vendor's page in a new tab)
In the SES console choose Configuration > Identities > Create identity and enter the domain
Leave publishing onsource (opens the vendor's page in a new tab)
Under Advanced DKIM settings, and under the custom MAIL FROM domain if you set one, leave Publish DNS records to Route53 Enabled
Publish latersource (opens the vendor's page in a new tab)
For an existing identity choose Publish DNS records to Route53 next to Edit in the DKIM or Custom MAIL FROM domain container on the Authentication tab
Hosted zone in another accountsource (opens the vendor's page in a new tab)
Copy the three CNAMEs from Publish DNS records and add them in that account's hosted zone by hand
Wait for Verifiedsource (opens the vendor's page in a new tab)
SES can take up to 72 hours to find the records; DKIM configuration then shows Successful and the identity Verified
Field values
What goes in each field in Amazon Route 53
Where: Route 53 console > Hosted zones > the domain's hosted zone > Create recordsource (opens the vendor's page in a new tab)
- Record name
- Leave blank (the domain itself)
- Record type
- TXT
- Value
- "v=spf1 include:<your provider> ~all"
- TTL (seconds)
- 300 while you set up
- Routing policy
- Simple routing
- Alias
- Off
- Record name
<selector>._domainkey- Record type
- CNAME or TXT, as your provider gives it
- Value
- The CNAME target, or the key in quotes, split into 255-character strings if longer
- TTL (seconds)
- 300 while you set up
- Routing policy
- Simple routing
- Alias
- Off
- Record name
_dmarc- Record type
- TXT
- Value
- "v=DMARC1; p=none; rua=mailto:<address>"
- TTL (seconds)
- 300 while you set up
- Routing policy
- Simple routing
- Alias
- Off
Step by step
Add a record in Amazon Route 53
TXT record: SPF, DMARC and DKIM keys
Open the hosted zonesource (opens the vendor's page in a new tab)
Sign in to the Route 53 console, choose Hosted zones in the navigation pane and choose the name of the domain's hosted zone
Create recordsource (opens the vendor's page in a new tab)
Choose Create record, keep Simple routing and set Record type to TXT
Record namesource (opens the vendor's page in a new tab)
Leave it blank for SPF on the domain itself, without an @. Enter _dmarc for DMARC or <selector>._domainkey for a DKIM key
Value in quotessource (opens the vendor's page in a new tab)
Enclose the value in double quotes. A key over 255 characters goes on one line as "<part 1>" "<part 2>"; a second value for the same name goes on its own line
Create recordssource (opens the vendor's page in a new tab)
Choose Create records. Changes generally reach all Route 53 name servers within 60 seconds
CNAME record: DKIM from a provider that hosts the key
Open the hosted zonesource (opens the vendor's page in a new tab)
Hosted zones > the name of the domain's hosted zone > Create record
Choose CNAMEsource (opens the vendor's page in a new tab)
Set Record type to CNAME, keep Alias off and enter only the part before your domain in Record name, such as <selector>._domainkey
Paste the targetsource (opens the vendor's page in a new tab)
In Value enter the full target your provider gives; the trailing dot is optional and a CNAME takes one value
Create recordssource (opens the vendor's page in a new tab)
Choose Create records, then repeat for each CNAME your provider lists
Amazon Route 53 specifics
Before you save
- Record name takes only the part before your domain, such as _dmarc, and stays empty for the domain itself; AWS says not to enter a value such as @source (opens the vendor's page in a new tab)
- AWS no longer recommends the SPF record type (RFC 7208, section 14.1); publish SPF as a TXT recordsource (opens the vendor's page in a new tab)
- With simple routing all TXT values for one name sit in one record, one value per line; add a verification string as a new line of the existing recordsource (opens the vendor's page in a new tab)
- One quoted string holds up to 255 characters and one TXT value up to 4,000; a longer DKIM key goes on one line as several quoted stringssource (opens the vendor's page in a new tab)
- Alias records point only to selected AWS resources or another record in the same hosted zone; a TXT value or a CNAME target at your provider goes in a record with Alias offsource (opens the vendor's page in a new tab)
- The records apply when the domain's registrar lists the four name servers from this hosted zone's NS recordsource (opens the vendor's page in a new tab)
- A domain registered with Route 53 gets a hosted zone automatically; records in any other hosted zone apply only after the domain switches to its name serverssource (opens the vendor's page in a new tab)
- When you change records on a domain already in use, AWS suggests a short TTL such as 300 seconds first, raised once the new settings check outsource (opens the vendor's page in a new tab)
Records by provider
The exact values each service asks for:
Troubleshooting
Common Amazon Route 53 errors and fixes
TXT value without quotes
Enclose each TXT string in double quotes, such as "v=spf1 include:<your provider> ~all"source (opens the vendor's page in a new tab)
DKIM key over 255 characters
Split it into strings of 255 characters or fewer, each in double quotes, and list them on the same line: "<part 1>" "<part 2>"source (opens the vendor's page in a new tab)
A TXT record already exists at that name
Select that record, add the new value on its own line in the Edit record pane and choose Save changes; simple routing keeps every TXT value for a name in one recordsource (opens the vendor's page in a new tab)
SPF saved as record type SPF
Create it again as a TXT record with the same value; AWS no longer recommends the SPF typesource (opens the vendor's page in a new tab)
CNAME at the root or next to other records
A CNAME cannot use the hosted zone's own name or share a name with any other record; DKIM CNAMEs go at <selector>._domainkeysource (opens the vendor's page in a new tab)
Domain twice: <selector>._domainkey.example.com.example.com
Remove the domain from the end of the record namesource (opens the vendor's page in a new tab)
Records saved, old answers still served
Compare the registrar's name servers with the hosted zone's NS record; with two hosted zones of the same name, edit the one the domain usessource (opens the vendor's page in a new tab)
Records added to a private hosted zone
A private hosted zone answers inside its VPCs; queries from outside resolve on the internet, so add the records to the public hosted zone for the domainsource (opens the vendor's page in a new tab)
SES DKIM pending on a Route 53 domain
Choose Publish DNS records to Route53 on the identity's Authentication tab, or add the three CNAMEs by hand; SES checks for up to 72 hourssource (opens the vendor's page in a new tab)
For cold email
Mailboxes that come with the DNS records done
Outreach2day buys the domains, publishes SPF, DKIM and DMARC, creates the mailboxes and starts warmup, then sends your campaigns from its own sequencer or exports the mailboxes to Instantly or Smartlead.
- SPF, DKIM and DMARC set for youOn every domain, checked after setup and kept in place
- $2.50 a mailbox a month12-mailbox minimum; warmup and the sending engine included
- 1,000+ mailboxesA volume price per mailbox, quoted on a call
Questions
How do I add a Route 53 SPF record?
Open Hosted zones, choose the domain's hosted zone and select Create record. Leave Record name blank, set Record type to TXT and enter the value in double quotes, such as "v=spf1 include:<your provider> ~all", then choose Create records. If a TXT record already exists at the root, edit it and add the SPF value on a new line, keeping one v=spf1 value for the domain.
Should an AWS Route 53 SPF record use the SPF type?
No. Route 53 still lists SPF as a record type, but AWS no longer recommends it: RFC 7208 says the SPF type is no longer appropriate for SPF version 1. Publish the same v=spf1 value as a TXT record.
How do I add an AWS Route 53 DKIM record?
Use the record type your provider gives. For a CNAME, choose Create record, enter the name your provider lists without your domain, such as <selector>._domainkey, in Record name, set Record type to CNAME with Alias off and paste the full target in Value. For a TXT key, set Record type to TXT and paste the key in double quotes, split into 255-character strings if it is longer.
What if the DKIM key is too long for Route 53?
Split the key into strings of 255 characters or fewer, put each string in double quotes and list them on the same line with a space between them: "<first 255 characters>" "<the rest>". One TXT value can hold up to 4,000 characters. Parts on separate lines become separate values, so the key breaks.
Where does the Route 53 DMARC record go?
Create a TXT record with Record name _dmarc and a quoted value such as "v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com". The Amazon SES guide suggests starting at p=none, moving to p=quarantine once the reports show all or most of your legitimate mail aligned with SPF or DKIM, and to p=reject as the last step.
Can a domain have two TXT records in Route 53?
With simple routing Route 53 keeps every TXT value for a name in one record, one value per line, so SPF and a verification string at the root share that record. Keep a single v=spf1 value in it and add each sending service's include to that value.
Does Amazon SES add its DKIM records to Route 53 automatically?
Yes, when the hosted zone is in the AWS account you send from. Leave Publish DNS records to Route53 enabled when you create the identity, or choose that button later on the identity's Authentication tab. For a hosted zone in another account, add the three CNAMEs by hand.
How long do Route 53 DNS changes take?
AWS says changes generally reach all Route 53 name servers within 60 seconds. Resolvers that cached the old record keep it until its TTL runs out, and a name looked up before the record existed can stay cached as missing for up to the SOA record's TTL, 900 seconds by default. A name server change at the registrar can take up to two days.
How do I set up SPF, DKIM and DMARC for cold email domains on Route 53?
Add the records your sending service lists in the domain's hosted zone, then run the check above. Outreach2day cold email infrastructure sets SPF, DKIM and DMARC automatically on domains bought in the app and on your own domains once their name servers point to us, which takes 24 to 48 hours. From then on those domains answer from our DNS, and their Route 53 hosted zone no longer applies.
Sources
Amazon Route 53 documentation, checked . Menus and values change; if a step differs, Amazon Route 53's own page is the reference.
- Creating records by using the Amazon Route 53 console (docs.aws.amazon.com)
- Values specific for simple records (docs.aws.amazon.com)
- Values that are common for all routing policies (docs.aws.amazon.com)
- Supported DNS record types (docs.aws.amazon.com)
- Choosing between alias and non-alias records (docs.aws.amazon.com)
- Editing records (docs.aws.amazon.com)
- Use your domain for a static website in an Amazon S3 bucket (docs.aws.amazon.com)
- NS and SOA records that Amazon Route 53 creates for a public hosted zone (docs.aws.amazon.com)
- Registering a new domain (docs.aws.amazon.com)
- I changed DNS settings, but they haven't taken effect (docs.aws.amazon.com)
- Working with private hosted zones (docs.aws.amazon.com)
- Creating and verifying identities in Amazon SES (docs.aws.amazon.com)
- Edit an identity using the SES console (docs.aws.amazon.com)
- Using a custom MAIL FROM domain (docs.aws.amazon.com)
- Complying with DMARC authentication protocol in Amazon SES (docs.aws.amazon.com)
Deliverability call
Talk to our deliverability team
Book a call with the people who run our mailbox infrastructure. We look at your current setup and tell you what to change. Running 1,000+ mailboxes? We also quote a volume price below every vendor list price in our comparisons, warmup and sending included.
- Review your domains, DNS records and current inbox placement
- Size the setup: domains, mailboxes per domain and daily volume per mailbox
- Plan warmup and the move from your current provider or sequencer
- 1,000+ mailboxes: a volume price per mailbox for your setup
Free call
See open times in your time zone and book on this page.
Or open the booking pageLoading available times…
Open the booking page instead