DNS Stale Resource Records Removal Mechanism
draft-janardhan-dnsext-aging-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Authors | Kamal Janardhan , Dr. Levon Esibov | ||
| Last updated | 2002-08-14 | ||
| 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
The Dynamic DNS Update Protocol assumes that the devices/applications performing dynamic registration of the DNS records will delete the records from the DNS database when the records become invalid. Initial deployment of the devices supporting the Dynamic DNS Update protocol indicated that there are multiple legitimate scenarios when records dynamically registered in DNS are not removed from the database by the devices that originally registered them. This can result in a substantial number of stale records. This document describes a mechanism to clean up these stale records.
Authors
Kamal Janardhan
Dr. Levon Esibov
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)