RFC 2308: Negative Caching of DNS Queries (DNS NCACHE)
In plain English — editorial summary, not part of the RFC
RFC1034 provided a description of how to cache negative responses. It however had a fundamental flaw in that it did not allow a name server to hand out those cached responses to other resolvers, thereby greatly reducing the effect of the caching. This document addresses issues raise in the light of experience and replaces RFC1034 Section 4.3.4. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2308
- Published
- March 1998
- Authors
- M. Andrews
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 19
- Also known as
- —
Topics
Referenced by
8 later RFCs formally update or obsolete part of this document.
- 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 6604xNAME RCODE and Status Bits ClarificationCurrent
April 2012
- RFC 8020NXDOMAIN: There Really Is Nothing UnderneathCurrent
November 2016
- RFC 8499DNS TerminologyObsoleted
January 2019
- RFC 9499DNS TerminologyCurrent
March 2024
- RFC 9520Negative Caching of DNS Resolution FailuresCurrent
December 2023
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 2671Extension Mechanisms for DNS (EDNS0)Obsoleted
August 1999
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2673Binary Labels in the Domain Name SystemObsoleted
August 1999
- RFC 2782A DNS RR for specifying the location of services (DNS SRV)Updated
February 2000
- RFC 2874DNS Extensions to Support IPv6 Address Aggregation and RenumberingUpdated
July 2000
- RFC 2930Secret Key Establishment for DNS (TKEY RR)Updated
September 2000
- RFC 2931DNS Request and Transaction Signatures ( SIG(0)s )Current
September 2000
- RFC 3007Secure Domain Name System (DNS) Dynamic UpdateCurrent
November 2000
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?