RFC 8020 - NXDOMAIN: There Really Is Nothing Underneath
- Status: Proposed Standard
- Published: November 2016
- Stream: IETF
- Updates: RFC 1034, RFC 2308
- Errata: RFC 8020 Errata
Document Information
- RFC Number: 8020
- Title: NXDOMAIN: There Really Is Nothing Underneath
- Authors: S. Bortzmeyer (AFNIC), S. Huque (Verisign Labs)
- Date: November 2016
- Category: Standards Track
- Updates: RFC 1034, RFC 2308
- ISSN: 2070-1721
Abstract
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.
Status of This Memo
This is an Internet Standards Track document.
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 7841.
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc8020.
Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
Table of Contents
- 1. Introduction and Background
- 2. Rules
- 3. Updates to RFCs
- 4. Benefits
- 5. Possible Issues
- 6. Implementation Considerations
- 7. Security Considerations
- 8. References
- Acknowledgments
- Authors' Addresses
Appendices
- Appendix A. Why can't we just use the owner name of the returned SOA?
- Appendix B. Related Approaches
Related Resources
- Official RFC: RFC 8020
- DataTracker: RFC 8020 Info
- Errata: RFC Editor Errata