Requirements for a Mechanism for Remote-Triggered DNS Cache Flushes
draft-jabley-dnsop-flush-reqs-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Joe Abley | ||
| Last updated | 2014-04-21 (Latest revision 2013-10-18) | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| 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) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
Operational calamaties in the DNS happen from time to time, and in many cases problems persist due to DNS caching of bad data. Lacking any robust mechanism to signal that bad data has been flushed, the operators of DNS authority servers often resort to unauthenticated requests for help being sent to mailing lists, the results of which are frequently unsatisfying to all concerned. This document aims to present requirements for a more robust mechanism by which authoritative server operators can signal to recursive server operators that bad data has been published, and that targetted cache flushes may be beneficial.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)