The DNS Extended Server Diagnostics (ESD) Option
draft-hunt-dns-server-diagnostics-00

Document Type Expired Internet-Draft (individual)
Author Evan Hunt
Last updated 2014-02-01 (Latest revision 2013-07-31)
Stream (None)
Formats
Expired & archived
plain text xml htmlized pdfized bibtex
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date (None)
Responsible AD (None)
Send notices to (None)
Email authors IPR References Referenced by Nits
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-hunt-dns-server-diagnostics-00.txt

Abstract

The widespread adoption of DNSSEC implies more frequent DNSSEC failures. Unfortunately, DNSSEC's failure mode is largely opaque to the client: when validation fails, the only signal that the clients of a validating resolver receive is an empty response with a SERVFAIL response code. This note proposes a protocol extension to allow SERVFAIL responses to include additional diagnostic information, giving the client greater insight into what went wrong and a better chance of delivering useful problem reports to DNS operators.

Authors

Evan Hunt

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