FREE & OPEN
THE OPEN PROTOCOL PLAYGROUND

Make every packet make sense.

Explore the conversations that connect our world. One packet at a time.

66 protocolsZero paywalls. Endless curiosity.

DNSSEC

Web & applicationIntermediate

Validate signed DNS data using a chain of trust.

SIMULATION01 / 04
Loading topology…
0.0s / 4.2s
01
STEP 1 OF 4Client → Server / peer

Query with DO bit

A validating resolver requests DNSSEC records through EDNS.

#TIMESOURCE → DESTINATIONMESSAGE
0.000192.0.2.10198.51.100.20Query with DO bit
1.400198.51.100.20192.0.2.10Answer + RRSIG
2.800192.0.2.10198.51.100.20DNSKEY query
4.200198.51.100.20192.0.2.10DNSKEY answer

Validate signed DNS data using a chain of trust.

Explain Query with DO bit and distinguish it from DNSKEY answer.

Prerequisites: DNS

Ready to test your understanding?

Rebuild the exchange. Read the fields. Find the mistakes.

Learn from the sourceRFC 4033Protocol guide

DNSSEC: protocol guide / panduan protokol

Validate signed DNS data using a chain of trust.

Validasi data DNS bertanda tangan melalui rantai kepercayaan.

Communication walkthrough / Alur komunikasi

  1. Query with DO bit

    A validating resolver requests DNSSEC records through EDNS.

    Resolver validasi meminta record DNSSEC melalui EDNS.

  2. Answer + RRSIG

    An RRSIG authenticates an RRset; it does not encrypt the answer.

    RRSIG mengautentikasi RRset; tidak mengenkripsi jawaban.

  3. DNSKEY query

    The resolver obtains zone keys and validates them against a trusted DS chain.

    Resolver mengambil kunci zona dan memvalidasinya terhadap rantai DS tepercaya.

  4. DNSKEY answer

    Successful validation requires correct signatures, delegation and validity times.

    Validasi memerlukan signature, delegasi, dan masa berlaku yang benar.

Source and simulation scope

This is a simplified, deterministic teaching scenario. Timing is illustrative. Messages grouped within one event are explicitly condensed. Hexadecimal fixtures, where shown, contain only the indicated protocol ADU, not a full network capture. No PCAP files are supplied.

RFC 4033 ↗