A Common Operational Problem in DNS Servers - Failure To Communicate.
draft-ietf-dnsop-no-response-issue-13

Document Type Expired Internet-Draft (dnsop WG)
Last updated 2019-08-29 (latest revision 2019-02-25)
Replaces draft-andrews-dns-no-response-issue
Stream IETF
Intended RFC status Best Current Practice
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Consensus: Waiting for Write-Up
Document shepherd Tim Wicinski
IESG IESG state Expired
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-ietf-dnsop-no-response-issue-13.txt

Abstract

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

Authors

Mark Andrews (marka@isc.org)
Ray Bellis (ray@isc.org)

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