Route 53 signs a hosted zone with algorithm 13, on a key-signing key you keep in AWS KMS. It does not publish the DS for you, even when the domain is on Route 53 Domains — and Route 53 Domains asks for the public key rather than a DS.
| What it is | Registrar and DNS host |
| DNSSEC | Yes — no Route 53 charge; the KMS key costs $1 a month plus its signing requests |
| Signing | You enable signing and create the key-signing key in AWS KMS; Route 53 manages the zone-signing key |
| Algorithm | ECDSAP256SHA256 (13), DS digest SHA-256 |
| DS record | No — even with the domain on Route 53 Domains, you add the key yourself |
Is DNSSEC working for your domain?
Enter a domain: we read the DS record at its registry and the keys its nameservers publish, check that they match and the signatures are current, and ask a validating resolver.
Turning it on at Amazon Route 53
- Before signing: lower the zone’s TTLs (AWS suggests at most one hour) and watch for two weeks.
- Hosted zones, the zone, DNSSEC signing, Enable DNSSEC signing: create the key-signing key on a customer managed KMS key (asymmetric ECC_NIST_P256, in US East — N. Virginia).
- Then View information to create DS record — for Route 53 Domains or another registrar.
- Set CloudWatch alarms on DNSSECInternalFailure and DNSSECKeySigningKeysNeedingAction.
The DS record
Route 53 Domains takes the public key rather than a digest — Registered domains, the domain, DNSSEC keys, Add key:
- Key type — KSK or ZSK
- Algorithm
- Public key (Base64) — the key itself, not the digest
Before moving the domain or its DNS
Turning it off: remove the DS (or the key at Route 53 Domains) first, wait out its TTL — AWS says up to three days at the registrar — then disable signing. The other way round, validating resolvers answer SERVFAIL.
Moving DNS to another provider: remove the DS first; signing cannot run at two providers at once.
Worth knowing
Route 53 uses compact denial of existence (“black lies”), so a signed zone cannot be walked.
Signed zones cap TTLs at one week, and AWS does not support multi-vendor signing.
Route 53 Domains takes up to 13 keys for .com and .net, and 4 for other endings.
Whose nameservers a domain uses: Amazon Route 53’s.
Sources
Checked on 27 September 2026 against these official sources:
- Configuring DNSSEC signing in Amazon Route 53 — docs.aws.amazon.com
- Enabling DNSSEC signing and establishing a chain of trust — docs.aws.amazon.com
- Working with customer managed keys for DNSSEC — docs.aws.amazon.com
- Configuring DNSSEC for a domain — docs.aws.amazon.com
- Disabling DNSSEC signing — docs.aws.amazon.com
- Amazon Route 53 pricing — aws.amazon.com
- Pricing — AWS Key Management Service (KMS) — aws.amazon.com