In Route 53, records live in a hosted zone. Leave the record name blank for the root — not @ — quote TXT values, and split anything longer than 255 characters yourself: Route 53 does not, and rejects a 2048-bit DKIM key pasted in one piece.
| Name field | Blank for the root; the subdomain part otherwise |
| TXT values | In double quotes; split over 255 characters by hand |
| Alias at the root | Alias records (to AWS resources) |
| Changes | On all Route 53 nameservers within about 60 seconds |
| Nameservers | ns-NNNN.awsdns-NN .com/.net/.org/.co.uk |
Where the DNS records are
In the Route 53 console, open Hosted zones, choose the zone, then Create record. DNSSEC is on the zone’s DNSSEC signing tab. Make sure the registrar lists the four nameservers of this hosted zone — every zone gets its own four.
What to type in the name field
In the console, enter only the part before your domain, and leave the name blank for the root — Route 53’s documentation says not to type @. The API and CLI take the full name instead.
| You were given a record for | Type in the name field |
|---|---|
| The domain itself — SPF, verification codes, MX | (leave blank) |
| DMARC | _dmarc |
| A DKIM key (selector s1, for example) | s1._domainkey |
| A subdomain such as www or mail | www |
Adding a record
- Open Hosted zones and choose the zone.
- Select Create record.
- Enter the record name as in the table above and choose the type.
- Enter the value — for TXT, in double quotes; several values for the same name go on separate lines of the same record.
- Set a TTL (Route 53 recommends 60 to 172,800 seconds) and select Create records.
Check the record you just added
Enter the full name — _dmarc.yourdomain.com, s1._domainkey.yourdomain.com — and the type. If it answers, it is published; if it is not there yet, try again after a few minutes.
TXT records and long DKIM keys
Route 53 does not split long values. A TXT string can be at most 255 characters, so a 2048-bit DKIM key must be entered as several quoted strings on one line — “first part” “second part” — or Route 53 rejects it (CharacterStringTooLong). Receivers join the parts back together.
Pointing the root domain at a service
Alias records can sit at the root, but only point to AWS resources — CloudFront, a load balancer, an S3 website, API Gateway — or another record in the same zone, not to an outside host name. Queries for aliases to AWS resources are free.
DNSSEC
Choose Enable DNSSEC signing on the zone; Route 53 uses a customer-managed KMS key, which AWS bills separately. Then view the DS information and, if the domain is registered elsewhere, add the DS record at that registrar. AWS advises lowering the zone’s TTLs to an hour first.
Common mistakes
- Typing @ for the root — leave the name blank.
- Pasting a 2048-bit DKIM key as one string: Route 53 rejects it; split it into quoted parts.
- TXT values without quotes.
- The registrar pointing at another hosted zone’s nameservers.
Setting up email? The exact records for each service are in our email setup guides; to watch a change reach resolvers worldwide, use the propagation checker.
Questions
How long do Route 53 changes take?
AWS says changes usually reach all Route 53 nameservers within 60 seconds; resolvers then follow the TTL of the record they cached.
Sources
Checked against Amazon Route 53’s own documentation on 25 September 2026:
- Creating records by using the Amazon Route 53 console — docs.aws.amazon.com
- Supported DNS record types — docs.aws.amazon.com
- Choosing between alias and non-alias records — docs.aws.amazon.com
- Enabling DNSSEC signing and establishing a chain of trust — docs.aws.amazon.com