AWS Security ChangesHomeSearch

AWS Route53: Clarify DNSSEC signing limited to public hosted zones

Service: Route53 · 2026-10-16 · Documentation medium

File: Route53/latest/DeveloperGuide/dns-configuring-dnssec.md · Type: network

Summary

Added a note that DNSSEC signing is supported only for public hosted zones (no KSKs or signing for private hosted zones) and points to Route 53 Resolver DNSSEC validation for VPC queries.

Security assessment

The added note documents a DNSSEC capability boundary and directs users to DNSSEC validation for VPC queries, which is security hardening guidance (DNS spoofing/cache-poisoning protection). It is not tied to a specific vulnerability or incident.

Evidence

+  * DNSSEC signing is supported only for public hosted zones. You can't create key-signing keys (KSKs) or enable DNSSEC signing for a private hosted zone. If you need DNSSEC validation for DNS queries from your VPCs, see [Enabling DNSSEC validation in Amazon Route 53](./resolver-dnssec-validation.html).

Diff

diff --git a/Route53/latest/DeveloperGuide/dns-configuring-dnssec.md b/Route53/latest/DeveloperGuide/dns-configuring-dnssec.md
index 36fcae1..aae9a20 100644
--- a//Route53/latest/DeveloperGuide/dns-configuring-dnssec.md
+++ b//Route53/latest/DeveloperGuide/dns-configuring-dnssec.md
@@ -14,0 +15,2 @@ Before you enable DNSSEC signing, note the following:
+  * DNSSEC signing is supported only for public hosted zones. You can't create key-signing keys (KSKs) or enable DNSSEC signing for a private hosted zone. If you need DNSSEC validation for DNS queries from your VPCs, see [Enabling DNSSEC validation in Amazon Route 53](./resolver-dnssec-validation.html).
+