# DNSSEC

DNSSEC is a set of DNS protocol extensions that uses digital signatures to authenticate DNS data and detect unauthorized modification.

Cloud concept. Updated 2026-10-29. Page: https://blowstack.com/tools/cloud-concepts-hub/dnssec

> DNSSEC lets validating resolvers verify that DNS answers originate from the authoritative zone and have not been altered, helping defend against forged responses and cache poisoning. It establishes trust through signed records and parent-to-child delegations, but it does not encrypt DNS queries or responses.

Practice exams covering DNSSEC: [ANS-C01 AWS Certified Advanced Networking - Specialty](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty).

## 6 key aspects of DNSSEC

DNSSEC combines signed DNS data, hierarchical trust, authenticated negative answers, and resolver validation, with careful key and delegation management.

1. **Cryptographic authenticity and integrity**: Digital signatures let validators detect forged or modified DNS record sets. DNSSEC does not conceal the queried name or returned records.
2. **Hierarchical chain of trust**: DNSKEY records publish signing keys, while DS records in parent zones connect child zones to the trust hierarchy. A signed zone without the necessary parent DS relationship is not automatically trusted through the public DNS root.
3. **Separate signing and validation**: Authoritative servers publish signed data, while recursive resolvers or validating clients check it. Deploy both functions where required instead of treating zone signing as protection for every client.
4. **Authenticated denial of existence**: NSEC and NSEC3 records allow validators to authenticate negative answers. This protects against fabricated claims that a name or record type does not exist.
5. **Validation-aware failure handling**: Answers that fail required validation normally result in SERVFAIL, while legitimately unsigned zones can still resolve. Investigate DS mismatches, missing keys, expired signatures, and timing problems before disabling validation.
6. **Coordinated key and delegation lifecycle**: Key rollovers and signing changes must account for cached DNSKEY and DS records. Coordinate DNS operators, registrar administrators, and key owners to avoid breaking the chain of trust.

## Cloud services for DNSSEC

Amazon Route 53 signs public hosted-zone data, using AWS KMS to support its key-signing key. The domain registrar or parent-zone operator publishes the DS record that connects that zone to the public DNS chain of trust. Route 53 Resolver can independently validate public DNS answers for workloads in a VPC. These controls protect different sides of DNS: authoritative signing protects published records, while recursive validation checks answers consumed by clients. In hybrid networks, forwarding rules determine the resolution path, so engineers must configure validation at the resolver actually responsible for it. Private hosted zones do not inherit DNSSEC protection from public-zone signing or Resolver validation.

- **[Amazon Route 53](https://blowstack.com/tools/cloud-services-hub/amazon-route-53)**: Provides DNSSEC signing for public hosted zones and publishes the required DNSKEY and RRSIG records. Establishing public trust also requires publishing the corresponding DS record in the parent zone, usually through the registrar.

## DNSSEC exam questions

Real practice exam questions on DNSSEC, with the correct answer and its explanation.

### Question 1 (ANS-C01)

**Question:**

A company manages the DNSSEC-signed public zone example.com in a networking AWS account. The zone delegates legacy.example.com to a DNSSEC-signed Route 53 public hosted zone in an application account. The delegation has valid NS and DS records, and the public DNSSEC chain currently validates successfully.

The company must permanently stop signing legacy.example.com while retaining its hosted zone, application records, and existing name servers. Security policy permits the child zone to become unsigned, but example.com must remain signed. Resolution must continue without DNSSEC validation failures for internet clients, including clients whose recursive resolvers have cached delegation records. The company does not control those resolvers.

Which procedure meets these requirements?

**Correct answer:** Remove the DS record for legacy.example.com from example.com. Confirm that the parent authoritative servers no longer serve it, and wait for previously cached DS records to expire. Then deactivate the child zone's KSK and disable signing for the child hosted zone.

**Explanation:** The parent's DS record establishes that the child must validate. Removing it while the child remains correctly signed allows cached DS records to remain usable until they expire. After those cached records expire, validators can authenticate the absence of a DS record and treat the child as an insecure, unsigned delegation. The parent can remain signed, and the existing NS delegation does not need to change.

## Practice DNSSEC in a full exam

Questions on DNSSEC in each practice exam, with every answer option and an explanation for each:

- [ANS-C01](https://blowstack.com/practice-exams/aws-certified-advanced-networking-specialty): 14 questions

## What is DNSSEC

Domain Name System Security Extensions, or DNSSEC, adds cryptographic authentication to DNS. Ordinary DNS does not inherently prove that an answer is authentic, so an attacker who successfully injects a forged response can redirect clients to an unintended address. DNSSEC allows a validating resolver to check signatures before accepting protected DNS data. Its protections depend on correct authoritative signing, a valid chain of trust, and validation along the client's resolution path.

DNSSEC signs resource record sets rather than individual packets. An RRSIG record carries a signature over a record set, such as the A records for www.example.com. DNSKEY records publish the zone's public keys. A Delegation Signer, or DS, record in the parent zone contains a digest identifying a child zone's signing key. A resolver follows these relationships from a configured trust anchor, normally the DNS root, through the parent zones to the requested zone. NSEC or NSEC3 records provide authenticated denial of existence, allowing a resolver to verify that a requested name or record type does not exist.

Authoritative signing and recursive validation are separate functions. A DNS hosting provider can sign a public zone, but clients using a nonvalidating resolution path do not automatically gain protection against forged answers. Conversely, enabling validation on a recursive resolver does not sign the domains an organization owns. A validating resolver distinguishes secure answers, unsigned or insecure answers, and bogus answers that fail expected validation. Unsigned DNS is not automatically rejected; a broken chain for a zone that should validate normally causes SERVFAIL.

For example, when securing example.com in a cloud public DNS service, first enable zone signing and verify that the authoritative servers publish the expected DNSKEY and RRSIG records. Then publish the corresponding DS record through the domain registrar so it appears in the parent zone. Simply adding an NS delegation, or publishing a DS record inside the child zone itself, does not establish the required parent-to-child trust relationship. Delegated subdomains require their own signing and DS configuration if they are to participate in the chain.

In Amazon Route 53, DNSSEC signing is available for public hosted zones, not private hosted zones. Route 53 manages the zone-signing key, while a key-signing key is backed by a customer managed asymmetric AWS KMS key. That KMS key must be in US East (N. Virginia), use the ECC\_NIST\_P256 key specification, and have SIGN\_VERIFY usage. Configure the required key policy, enable signing, and publish the generated DS details in the parent zone. Route 53 Resolver DNSSEC validation is a separate VPC setting for public DNS resolution; it does not validate private hosted-zone data or DNS responses obtained through forwarding rules.

Hybrid and multi-account designs must therefore identify where validation actually occurs. If an on-premises resolver forwards public queries to a cloud resolver, confirm that the receiving resolution path validates those queries. If cloud queries are forwarded to on-premises DNS, configure validation where that forwarded resolution is performed rather than assuming a VPC setting protects every answer. Signing keys, parent-zone DS records, and resolver settings may also belong to different accounts or teams, requiring coordinated changes.

Operational trade-offs include larger DNS responses, additional validation work, key-management responsibilities, and the possibility of resolution failures after configuration mistakes. Permit both UDP and TCP port 53 where DNS transport requires them, because larger responses can require TCP fallback. Plan key rollovers around DNSKEY and DS cache lifetimes, and never remove a key while cached trust information still depends on it. When disabling signing, remove the parent DS record and allow relevant caches to expire before stopping signatures. Monitor signing health, key accessibility, signature expiration, and validation failures.

DNSSEC provides authenticity and integrity, not confidentiality, service availability, or proof that an application is trustworthy. DNS over TLS and DNS over HTTPS encrypt a DNS transport connection; they complement rather than replace DNSSEC. HTTPS is still needed to authenticate and encrypt application traffic. During troubleshooting, requesting DNSSEC records with dig +dnssec does not itself validate them; use a validating tool or a trusted validating resolver and interpret its validation result.
