Skip to content
nofeb

SPF, DKIM, DMARC and MX on Amazon Route 53

DNS host detected from nameservers under *.awsdns-*

On Amazon Route 53, add the records by hand in Amazon Route 53's DNS form: full names with a trailing dot, TXT in double quotes, MX priority inside the value. nofeb detects Amazon Route 53 and returns each record in that shape.

Checked against the engine on .

How does nofeb know the domain is on Amazon Route 53?

It looks up the zone's NS records and matches the nameserver hostnames. Nameservers under awsdns-* mean Amazon Route 53. When a zone is split between two hosts during a move, the host serving most of its nameservers wins.

How do I add the records on Amazon Route 53?

Open Amazon Route 53's DNS page for the domain (Amazon Route 53 DNS console) and add each record from the table below. Then ask nofeb to check: POST /v1/domains/{domain_id}/verify.

What is specific to Amazon Route 53?

  • The Route 53 export is an UPSERT change batch for aws route53 change-resource-record-sets --hosted-zone-id Z… --change-batch file://batch.json.
  • UPSERT replaces a whole record set, so merge in any values already at those names first, for example existing MX records at the apex.
  • TXT values longer than 255 characters are split into several quoted strings in the batch and in Terraform, which is what Route 53's CharacterStringTooLong error asks for.

What exactly do I type in Amazon Route 53's record form?

Shown for example.com as Amazon Route 53 wants it; placeholder values come from your dns-setup response.

RecordTypeName boxValue boxPriority
DKIM key 1 CNAME token1._domainkey.example.com. target-1-from-nofeb —
DKIM key 2 CNAME token2._domainkey.example.com. target-2-from-nofeb —
DKIM key 3 CNAME token3._domainkey.example.com. target-3-from-nofeb —
MAIL FROM MX MX bounce.example.com. 10 feedback-host-from-nofeb in value
MAIL FROM SPF TXT bounce.example.com. "v=spf1 include:<value from nofeb> ~all" —
DMARC TXT _dmarc.example.com. "v=DMARC1; p=none; rua=mailto:dmarc@example.com" —
Inbound MX (optional) MX example.com. 10 inbound-host-from-nofeb in value

Which form rules does Amazon Route 53 follow?

  • Amazon Route 53 takes the full record name with a trailing dot in the name box, for example bounce.example.com.
  • TXT values go in double quotes: paste them with the quotes. Values over 255 characters are split into several quoted strings.
  • MX priority goes in the value box: 10 host, not a separate field.
  • In the Route 53 console, the Record name box takes only the prefix (bounce, or empty for the apex); the console shows .example.com after it. The API, CLI and change batches use the full name.

What goes wrong most often on Amazon Route 53?

  1. A name typed without its trailing dot or without the domain, which creates a record in the wrong place.
  2. A TXT value pasted without quotes, or a long value not split into 255-character strings.

Can I manage the records on Amazon Route 53 with Terraform?

Yes. The dns-setup response includes Terraform using the aws_route53_record resource for every record. The DMARC record looks like this:

Terraform for Amazon Route 53
variable "route53_zone_id" {
  type        = string
  description = "Hosted zone ID of example.com"
}

resource "aws_route53_record" "dmarc" {
  zone_id = var.route53_zone_id
  name    = "_dmarc.example.com"
  type    = "TXT"
  ttl     = 3600
  records = ["v=DMARC1; p=none; rua=mailto:dmarc@example.com"]
}

# MX records are emitted as "10 host" in records = [...]
Publishing email DNS records on Amazon Route 53 Add a domain; nofeb detects the DNS host from its NS records. Then one of three paths: a one-click Domain Connect link (Beta), publishing through the host's API with a token used once (Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun, Gandi), or instructions written for that host plus zone-file, Route 53 and Terraform exports. Every record is then checked live, showing what was found and the likely mistake, and domain.verified is emitted when all pass. Add the domain POST /v1/domains records generated Detect the DNS host from its nameservers GET …/dns-setup One-click Domain Connect sign in at the host, click Connect Beta Published through the API token used for one call, never stored POST …/dns/apply Instructions for that host host and value boxes, as its form wants zone file · Route 53 · Terraform Live check found value and likely fix domain.verified
nofeb looks up who runs Amazon Route 53 from its nameservers, takes the shortest path that host allows, then checks every record live until domain.verified fires.

Frequently asked questions

Do I type the full domain in Amazon Route 53's name field?

Yes. Amazon Route 53 takes fully qualified names with a trailing dot, for example bounce.example.com..

Does Amazon Route 53 need quotes around TXT values like DMARC?

Yes. Paste "v=DMARC1; p=none; rua=mailto:dmarc@example.com" including the quotes; Amazon Route 53 stores the value as typed.

Where are the DNS records in Amazon Route 53?

In Amazon Route 53's DNS page: console.aws.amazon.com/route53/v2/hostedzones. The dns-setup response links the same page for your domain.

Can nofeb add the records on Amazon Route 53 automatically?

Not by API token. Amazon Route 53 gets the records shaped for its form.

Status of everything on this page

Every capability named above, with its status as reconciled against the engine.

CapabilityWhat it doesStatus
Custom domains Add a domain and nofeb returns its DKIM, custom MAIL FROM and DMARC records, plus an inbound MX if you want nofeb to receive its mail, checks them, and emits domain.verified when they pass. Shipped
DNS setup made easy nofeb detects who hosts your domain's DNS and gives you the shortest path for that host. It can publish the records through the Cloudflare, DigitalOcean, Hetzner DNS, Vercel, Porkbun or Gandi API with a token used for that one call and never stored, and it never deletes a record. Every other host gets step-by-step instructions in its own terms, plus zone-file, Route 53 and Terraform exports. A live check shows each record's status, what was found and the likely mistake. Pointing your MX at nofeb is a separate choice, so publishing sending records never moves your mail. Shipped
Inbound mail server that checks mail at the door nofeb's own MX receives mail for the shared domain and your custom domains, with STARTTLS. It checks every recipient before accepting any data, verifies SPF, DKIM, ARC and DMARC, and scans for spam and viruses before it answers. Mail that fails a DMARC reject policy, carries a virus or is clearly spam is refused during delivery instead of bounced later; likely spam and DMARC-quarantined mail is filed into Junk. Every message carries a security verdict with its authentication, spam, virus and TLS results. Shipped