NXDOMAIN really means there is nothing underneath
draft-bortzmeyer-dnsop-nxdomain-cut-02
Document | Type |
Replaced Internet-Draft
(dnsop WG)
Expired & archived
|
|
---|---|---|---|
Authors | Stéphane Bortzmeyer , Shumon Huque | ||
Last updated | 2015-12-20 (Latest revision 2015-11-29) | ||
Replaced by | draft-ietf-dnsop-nxdomain-cut | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | Proposed Standard | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | Tim Wicinski | ||
IESG | IESG state | Replaced by draft-ietf-dnsop-nxdomain-cut | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | "Tim Wicinski" <tjw.ietf@gmail.com> |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document states clearly that when a DNS resolver receives a response with response code NXDOMAIN, it means that the name in the question section AND ALL THE NAMES UNDER IT do not exist. REMOVE BEFORE PUBLICATION: this document should be discussed in the IETF DNSOP (DNS Operations) group, through its mailing list. The source of the document, as well as a list of open issues, is currently kept at Github [1].
Authors
Stéphane Bortzmeyer
Shumon Huque
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)