Skip to main content

Requirements for Management of Name Servers for the DNS

Document Type Replaced Internet-Draft (individual)
Expired & archived
Author Wes Hardaker
Last updated 2008-08-29 (Latest revision 2008-05-20)
Replaced by RFC 6168
RFC stream (None)
Intended RFC status (None)
Stream Stream state (No stream defined)
Consensus boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-dnsop-name-server-management-reqs
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:


Management of name servers for the Domain Name Service (DNS) has traditionally been done using vendor-specific monitoring, configuration and control methods. Although some service monitoring platforms can test the functionality of the DNS itself there is not a interoperable way to manage (monitor, control and configure) the internal aspects of a name server itself. This document discusses the requirements of a management system for DNS name servers. A management solution that is designed to manage the DNS can use this document as a shopping list of needed features.


Wes Hardaker

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