OnlineHostings.in · Powering Your Digital Growth.
Get Started
Home / Domains / DNSSEC
DOMAIN SECURITY GUIDE

Protect DNS responses with DNSSEC validation.

DNS Security Extensions (DNSSEC) add cryptographic signatures to DNS data. Validating resolvers can use those signatures to check that DNS responses are authentic and have not been altered in transit.

  • Understand the DNSSEC chain of trust
  • Learn DNSKEY, DS and RRSIG roles
  • Plan activation and key changes carefully
✓
DNSSEC CHAIN OF TRUST
Root trust anchor↓Parent zone DS↓Child zone DNSKEY↓Signed DNS data
Conceptual illustration — not a live validation result
WHAT DNSSEC DOES

DNS data that can be cryptographically validated

Traditional DNS lookups do not, by themselves, provide a cryptographic way for a resolver to verify that an answer came from the correct zone and was not modified. DNSSEC adds digital signatures and a chain of trust so a validating resolver can detect invalid or missing signed data.

01

Authenticity

Signatures allow a validating resolver to verify that DNS data is consistent with the zone's published public keys.

02

Integrity

Validation can detect DNS data that has been modified or does not match its cryptographic signature.

03

Authenticated denial

Signed denial-of-existence records can help prove that a requested name or record type does not exist in the signed zone.

DNSSEC does not encrypt DNS queries or answers, hide domain names, secure a website by itself, or replace TLS/HTTPS, access controls and server security.

DNSSEC RECORDS

Know the records involved

DNSSEC uses several DNS record types and signatures. The DNS provider and registrar may display these details in different ways.

DNSKEY

Public zone key

Publishes the public key material used to verify signatures for the zone. The corresponding private key must be protected by the DNS operator.

DS

Delegation Signer

A digest of a child zone's DNSKEY, published in the parent zone. It connects the parent zone's trust to the child zone.

RRSIG

Resource Record Signature

Contains a digital signature covering a DNS record set, along with validity and key-tag information used during verification.

NSEC / NSEC3

Authenticated denial

Records used to prove that a queried name or record type does not exist. The selected method depends on the DNS implementation.

THE CHAIN OF TRUST

Parent and child zones must agree

DNSSEC validation follows a chain from a trust anchor through parent and child zones. The parent publishes a DS record that must match the relevant DNSKEY in the child zone. The child zone's signatures are then checked using its keys.

1. Trust anchor

A validating resolver starts with a configured trust anchor, commonly the DNS root key.

2. Parent zone

The parent zone supplies a signed DS record for the delegated child zone.

3. Child zone

The child zone publishes DNSKEY records and signed DNS data, including RRSIG records.

4. Validation result

The resolver checks the signatures and DS-to-DNSKEY relationship. A broken chain can cause validating resolvers to reject answers.

ACTIVATION CHECKLIST

Before enabling DNSSEC for a domain

DNSSEC activation involves both the DNS hosting provider and the registrar or parent-zone operator. Follow the exact sequence and values supplied by those providers.

Confirm provider support

Verify that the authoritative DNS provider supports DNSSEC signing for the domain and can provide the required DS data or an approved automated workflow.

Confirm registrar support

Check that the registrar can publish DS records in the parent zone for the domain's TLD.

Copy exact DS details

Use the complete key tag, algorithm, digest type and digest exactly as supplied. Do not derive or guess these values.

Check delegation

Confirm that the domain's active nameservers point to the zone that is being signed and that the DNSSEC data corresponds to that zone.

Validate after changes

Use independent DNSSEC validation tools and check from validating resolvers. Allow for applicable DNS caching and parent-zone publication.

Keep recovery access

Know the provider's documented recovery and DS-removal procedure before making changes, especially during a nameserver migration.

VALIDATION & TROUBLESHOOTING

Useful DNSSEC checks

Run checks from a trusted system and interpret the output with your DNS provider's documentation. Replace the example domain with one you are authorised to inspect.

Request DNSSEC data

dig example.com DNSKEY +dnssecdig example.com A +dnssec

The DNSSEC flag requests DNSSEC-related records where available; it does not by itself prove that the full chain validates.

Inspect the DS record

dig example.com DS +dnssec

Check the parent-published DS information and compare it with the DNS provider's current instructions.

Use a validating tool

delv example.com

Where available, a DNSSEC-aware validator can provide more useful validation diagnostics than a basic lookup.

Common failure: DS/DNSKEY mismatch

If a DS record in the parent zone does not match the active DNSKEY set in the child zone, validating resolvers may return SERVFAIL. Other causes include expired or missing signatures, incorrect time, incomplete signing and stale delegation data. Do not remove or replace DS records without confirming the correct recovery steps with the DNS provider and registrar.

KEY ROLLOVER & MIGRATION

Plan DNSSEC changes as a coordinated operation

Changing DNS providers

Before changing nameservers, confirm whether the new provider supports DNSSEC and obtain its key and DS instructions. Coordinate parent DS changes with the new zone's signing state. An old DS record left in place after the old key is no longer served can break validation.

Key rollover

DNSSEC key rollover must follow a provider-supported procedure so resolvers can validate during the transition. Timing, overlapping keys and parent DS updates matter. Do not manually replace keys or DS values based on a generic checklist.

Disabling DNSSEC

Disabling signing and removing the parent DS are separate actions. Follow the registrar and DNS provider's documented order to avoid a period in which the parent still points to keys that are no longer available.

DNSSEC FAQ

Frequently asked questions

Is DNSSEC the same as SSL or HTTPS?

No. DNSSEC validates DNS data using cryptographic signatures. TLS certificates and HTTPS protect connections between clients and websites. They address different parts of the security model.

Does DNSSEC encrypt DNS traffic?

No. DNSSEC provides authentication and integrity validation for DNS data; it does not encrypt DNS queries or responses.

Where do I get the DS record?

Your DNS hosting provider or DNSSEC signing service should supply the DS details or an automated registrar integration. Use the values generated for the active signed zone.

Can an incorrect DS record affect my website?

Yes. If the parent DS does not match the child zone's DNSKEY, validating resolvers can reject DNS answers, potentially making the domain appear unavailable to affected users.

Can I enable DNSSEC from this page?

No. This is an informational guide. It does not access a registrar, publish DS records, sign a DNS zone or perform live DNSSEC validation.

NEED HELP WITH DNSSEC?

Coordinate your DNSSEC setup safely.

Share your domain, registrar and authoritative DNS provider. Never send passwords, private keys, authentication tokens or other account credentials.

Request DNSSEC Assistance