RFC 7958: DNSSEC Trust Anchor Publication for the Root Zone
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9718.
Current version: RFC 9718 — DNSSEC Trust Anchor Publication for the Root Zone
In plain English — editorial summary, not part of the RFC
The root zone of the Domain Name System (DNS) has been cryptographically signed using DNS Security Extensions (DNSSEC). In order to obtain secure answers from the root zone of the DNS using DNSSEC, a client must configure a suitable trust anchor. This document describes the format and publication mechanisms IANA has used to distribute the DNSSEC trust anchors.
Document record
- Document ID
- RFC7958
- Published
- August 2016
- Authors
- J. Abley; J. Schlyter; G. Bailey; P. Hoffman
- Status
- INFORMATIONAL
- Stream
- INDEPENDENT
- Area
- —
- Pages
- 14
- Also known as
- —
- Obsoleted by:
- RFC 9718
Topics
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8509A Root Key Trust Anchor Sentinel for DNSSECCurrent
December 2018
- RFC 9120Nameservers for the Address and Routing Parameter Area ("arpa") DomainCurrent
October 2021
- RFC 2860Memorandum of Understanding Concerning the Technical Work of the Internet Assigned Numbers AuthorityCurrent
June 2000
- RFC 7314Extension Mechanisms for DNS (EDNS) EXPIRE OptionCurrent
July 2014
- RFC 8726How Requests for IANA Action Will Be Handled on the Independent StreamCurrent
November 2020
- RFC 7085Top-Level Domains That Are Already DotlessCurrent
December 2013
- RFC 6927Variants in Second-Level Names Registered in Top-Level DomainsCurrent
May 2013
- RFC 9199Considerations for Large Authoritative DNS Server OperatorsCurrent
March 2022
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?