Skip to content
AdminKit

ZONEMD record

What is ZONEMD record?

ZONEMD, defined in RFC 8976, is a DNS record holding a cryptographic digest of an entire zone's contents, letting a receiver verify a copy matches what the primary server published. It fills a gap DNSSEC's per-record RRSIG signatures don't cover -- AdminKit's AXFR guide explains the zone transfer a ZONEMD digest checks.

By AdminKit team, Netbase JSC · Updated

ZONEMD, defined in RFC 8976 (current document status at its IETF Datatracker entry), is a DNS record type that holds a cryptographic digest — a hash — of an entire zone’s contents, letting anything that receives a copy of the zone verify that copy matches what the primary server actually published. The specific hash algorithms and digest schemes a ZONEMD record can use are tracked in the ZONEMD Schemes and ZONEMD Hash Algorithms tables of IANA’s DNS Parameters registry. A secondary name server (or any other party that obtains a zone, such as over a zone transfer (AXFR)) can recompute the digest over the records it received and compare it to the ZONEMD record included in that same zone, catching accidental corruption or tampering that occurred somewhere between the primary and the receiver. Unbound’s unbound.conf reference offers a zonemd-check option for the zones it loads as an auth-zone, describing the ZONEMD record as a checksum over the zone data that, when a DNSSEC chain of trust exists, is checked together with its DNSSEC signatures. On the authoritative side, Knot DNS’s configuration reference provides zonemd-verify to check that a valid ZONEMD record is present on each zone load or update, and zonemd-generate to compute one with SHA-384 or SHA-512 and add it to the zone.

This fills a gap that DNSSEC doesn’t cover on its own: DNSSEC’s RRSIG signatures authenticate individual records, but nothing in ordinary DNS attests to the completeness and integrity of an entire zone as a single unit, which matters most for zones distributed outside the normal primary-to-secondary path, such as the root zone or files published for offline verification. ZONEMD is optional and additive — a resolver or secondary that doesn’t understand the record type simply ignores it, so publishing one doesn’t break compatibility with older software.

AdminKit groups zONEMD record under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

What does a ZONEMD record hold?

A cryptographic digest of an entire DNS zone's contents, defined in RFC 8976.

What gap does ZONEMD fill that DNSSEC does not cover on its own?

DNSSEC's RRSIG signatures authenticate individual records, but nothing in ordinary DNS attests to the completeness and integrity of an entire zone as a single unit.

Who can use a ZONEMD digest to verify a zone?

A secondary name server, or any other party that obtains a copy of the zone such as over a zone transfer (AXFR), by recomputing the digest and comparing it to the published ZONEMD record.

Does publishing a ZONEMD record break compatibility with older software?

No -- it is optional and additive; a resolver or secondary that does not understand the record type simply ignores it.