Configuration Issues Facing Full Service DNS Resolvers In The Presence of Private Network Addressing
draft-andrews-full-service-resolvers-02
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Mark P. Andrews | ||
| Last updated | 2006-02-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
Practice has shown that there are a number of zones all full service resolvers should, unless configured otherwise, automatically serve. RFC4193 already specifies that this should occur for D.F.IP6.ARPA. This document extends the practice to cover the IN-ADDR.ARPA zones for RFC1918 address space and other well known zones with similar usage constraints.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)