RFC 8020: NXDOMAIN: There Really Is Nothing Underneath
In plain English — editorial summary, not part of the RFC
This document states clearly that when a DNS resolver receives a response with a response code of NXDOMAIN, it means that the domain name which is thus denied AND ALL THE NAMES UNDER IT do not exist. This document clarifies RFC 1034 and modifies a portion of RFC 2308: it updates both of them.
Document record
- Document ID
- RFC8020
- Published
- November 2016
- Authors
- S. Bortzmeyer; S. Huque
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- ops
- Pages
- 10
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8022A YANG Data Model for Routing ManagementObsoleted
November 2016
- RFC 8027DNSSEC Roadblock AvoidanceCurrent
November 2016
- RFC 8040RESTCONF ProtocolUpdated
January 2017
- RFC 7999BLACKHOLE CommunityCurrent
October 2016
- RFC 8049YANG Data Model for L3VPN Service DeliveryObsoleted
February 2017
- RFC 8050Multi-Threaded Routing Toolkit (MRT) Routing Information Export Format with BGP Additional Path ExtensionsCurrent
May 2017
- RFC 8056Extensible Provisioning Protocol (EPP) and Registration Data Access Protocol (RDAP) Status MappingCurrent
January 2017
- RFC 8063Key Relay Mapping for the Extensible Provisioning ProtocolCurrent
February 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?