RFC 3007:Secure Domain Name System (DNS) Dynamic U...
RFC-Ref

RFC - 3007

Secure Domain Name System (DNS) Dynamic Update

Original: ftp://ftp.isi.edu/in-notes/rfc3007.txt
Authors: B. Wellington [Nominum]
Date: November 2000
Category: Proposed Standard



Obsoletes:
RFC-2137 Secure Domain Name System Dynamic Update (Obsoleted by RFC-3007prop)

Updates:
RFC-2535 Domain Name System Security Extensions (Obsoleted by RFC-4033prop, RFC-4035prop, RFC-4034prop) (Updated by RFC-3755, RFC-3757, RFC-3226prop, RFC-3658, RFC-3655, RFC-3007prop, RFC-3008, RFC-3845, RFC-3597prop, RFC-3445, RFC-3090, RFC-2931prop)
RFC-2136prop Dynamic Updates in the Domain Name System (DNS UPDATE) (Updated by RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-3007prop)

Updated by:
RFC-4035prop Protocol Modifications for the DNS Security Extensions (Updated by RFC-4470prop)
RFC-4034prop Resource Records for the DNS Security Extensions (Updated by RFC-4470prop)
RFC-4033prop DNS Security Introduction and Requirements

Referred by: 24 RFC
Refers to: 9 RFC

Status

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This document proposes a method for performing secure Domain Name System (DNS) dynamic updates. The method described here is intended to be flexible and useful while requiring as few changes to the protocol as possible. The authentication of the dynamic update message is separate from later DNSSEC validation of the data. Secure communication based on authenticated requests and transactions is used to provide authorization.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].


About Resource

Google
Web
RFC-Ref