RFC 2010: Operational Criteria for Root Name Servers
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 2870.
Current document in this lineage: RFC 7720 — DNS Root Name Service Protocol and Deployment Requirements
In plain English — editorial summary, not part of the RFC
This document specifies the operational requirements of root name servers, including host hardware capacities, name server software revisions, network connectivity, and physical environment. This memo provides information for the Internet community. This memo does not specify an Internet standard of any kind.
Document record
- Document ID
- RFC2010
- Published
- October 1996
- Authors
- B. Manning; P. Vixie
- Status
- INFORMATIONAL
- Stream
- Legacy
- Area
- —
- Pages
- 7
- Also known as
- —
- Obsoleted by:
- RFC 2870
Topics
Standards lineage
This document is one revision in a chain of 3 RFCs, each formally replacing the one before it.
- RFC 2010 (1996)
- RFC 2870 (2000)
- RFC 7720 (2015) ✓
Read the full history of DNS Root Name Service Protocol and Deployment Requirements →
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 2217Telnet Com Port Control OptionCurrent
October 1997
- RFC 1713Tools for DNS debuggingCurrent
November 1994
- RFC 2790Host Resources MIBCurrent
March 2000
- RFC 3109Request to Move STD 39 to Historic StatusCurrent
May 2001
- RFC 3234Middleboxes: Taxonomy and IssuesCurrent
February 2002
- RFC 663Lost message detection and recovery protocolCurrent
November 1974
- RFC 606Host names on-lineCurrent
December 1973
- RFC 1918Address Allocation for Private InternetsUpdated
February 1996
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?