Reverse DNS Status Report
draft-anderson-reverse-dns-status-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Dean Anderson | ||
| Last updated | 2007-04-24 | ||
| 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
Translation of IP addresses to domain names is an optional feature of DNS. Many sites implement it in someway, many others do not implement it at all. Over time, some myths have developed regarding reverse DNS mapping. The goal of this document is to to identify best practices, illuminate false assumptions and to report on the status of reverse DNS facilities so that DNS Administrators and operators can make informed decisions about the options for DNS reverse mapping.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)