RFC 6781: DNSSEC Operational Practices, Version 2
In plain English — editorial summary, not part of the RFC
This document describes a set of practices for operating the DNS with security extensions (DNSSEC). The target audience is zone administrators deploying DNSSEC. The document discusses operational aspects of using keys and signatures in the DNS. It discusses issues of key generation, key storage, signature generation, key rollover, and related policies. This document obsoletes RFC 4641, as it covers more operational ground and gives more up-to-date requirements with respect to key sizes and the DNSSEC operations.
Document record
- Document ID
- RFC6781
- Published
- December 2012
- Authors
- O. Kolkman; W. Mekking; R. Gieben
- Status
- INFORMATIONAL
- Stream
- IETF
- Area
- ops
- Pages
- 71
- Also known as
- —
- Obsoletes:
- RFC 4641
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2541 (1999)
- RFC 4641 (2006)
- RFC 6781 (2012)
Read the full history of DNSSEC Operational Practices, Version 2 →
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 6841A Framework for DNSSEC Policies and DNSSEC Practice StatementsCurrent
January 2013
- RFC 7344Automating DNSSEC Delegation Trust MaintenanceUpdated
September 2014
- RFC 7646Definition and Use of DNSSEC Negative Trust AnchorsCurrent
September 2015
- RFC 7828The edns-tcp-keepalive EDNS0 OptionCurrent
April 2016
- RFC 7901CHAIN Query Requests in DNSCurrent
June 2016
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8078Managing DS Records from the Parent via CDS/CDNSKEYUpdated
March 2017
- RFC 8145Signaling Trust Anchor Knowledge in DNS Security Extensions (DNSSEC)Updated
April 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?