RFC 2181: Clarifications to the DNS Specification
In plain English — editorial summary, not part of the RFC
This document considers some areas that have been identified as problems with the specification of the Domain Name System, and proposes remedies for the defects identified. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2181
- Published
- July 1997
- Authors
- R. Elz; R. Bush
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 14
- Also known as
- —
Topics
Referenced by
7 later RFCs formally update or obsolete part of this document.
- RFC 2535Domain Name System Security ExtensionsObsoleted
March 1999
- RFC 4033DNS Security Introduction and RequirementsUpdated
March 2005
- RFC 4034Resource Records for the DNS Security ExtensionsUpdated
March 2005
- RFC 4035Protocol Modifications for the DNS Security ExtensionsUpdated
March 2005
- RFC 4343Domain Name System (DNS) Case Insensitivity ClarificationUpdated
January 2006
- RFC 5452Measures for Making DNS More Resilient against Forged AnswersCurrent
January 2009
- RFC 8767Serving Stale Data to Improve DNS ResiliencyCurrent
March 2020
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2182Selection and Operation of Secondary DNS ServersCurrent
July 1997
- RFC 1996A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)Current
August 1996
- RFC 1995Incremental Zone Transfer in DNSUpdated
August 1996
- RFC 1982Serial Number ArithmeticCurrent
August 1996
- RFC 1886DNS Extensions to support IP version 6Obsoleted
December 1995
- RFC 2606Reserved Top Level DNS NamesUpdated
June 1999
- RFC 2845Secret Key Transaction Authentication for DNS (TSIG)Obsoleted
May 2000
- RFC 3090DNS Security Extension Clarification on Zone StatusObsoleted
March 2001
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?