A Common Operational Problem in DNS Servers - Failure To Respond.
draft-andrews-dns-no-response-issue-16

Document Type Replaced Internet-Draft (dnsop WG)
Last updated 2015-11-28 (latest revision 2015-11-26)
Replaced by draft-ietf-dnsop-no-response-issue
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state Adopted by a WG
Document shepherd Tim Wicinski
IESG IESG state Replaced by draft-ietf-dnsop-no-response-issue
Consensus Boilerplate Unknown
Telechat date
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 can be found at
https://www.ietf.org/archive/id/draft-andrews-dns-no-response-issue-16.txt

Abstract

The DNS is a query / response protocol. Failure to respond or to respond correctly to queries causes both immediate operational problems and long term problems with protocol development. This document identifies a number of common classes of queries to which some servers either fail to respond or else respond incorrectly. This document also suggests procedures for TLD and other similar zone operators to apply to help reduce / eliminate the problem. The document does not look at the DNS data itself, just the structure of the responses.

Authors

Mark Andrews (marka@isc.org)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)