RFC - 2136
Dynamic Updates in the Domain Name System (DNS UPDATE)
| Original: | ftp://ftp.isi.edu/in-notes/rfc2136.txt |
|---|---|
| Authors: | P. Vixie, Editor [ISC], S. Thomson [Bellcore], Y. Rekhter [Cisco], J. Bound [DEC] |
| Date: | April 1997 |
| Category: | Proposed Standard |
| Updates: | |
|---|---|
| RFC-1035std13 [STD 13] |
Domain names - implementation and specification (Updated by RFC-1876exp, RFC-1348, RFC-4033prop, RFC-4035prop, RFC-4034prop, RFC-2308prop, RFC-2065, RFC-2845prop, RFC-2181prop, RFC-1995prop, RFC-1996prop, RFC-2535, RFC-4343prop, RFC-3658, RFC-1982prop, RFC-2136prop, RFC-3425prop, RFC-1101, RFC-1183exp, RFC-2137) |
| 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 |
| RFC-3007prop | Secure Domain Name System (DNS) Dynamic Update (Updated by RFC-4033prop, RFC-4035prop, RFC-4034prop) |
| Referred by: | 39 RFC |
| Refers to: | 6 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.
Abstract
The Domain Name System was originally designed to support queries of a statically configured database. While the data was expected to change, the frequency of those changes was expected to be fairly low, and all updates were made as external edits to a zone's Master File.
Using this specification of the UPDATE opcode, it is possible to add or delete RRs or RRsets from a specified zone. Prerequisites are specified separately from update operations, and can specify a dependency upon either the previous existence or nonexistence of an RRset, or the existence of a single RR.
UPDATE is atomic, i.e., all prerequisites must be satisfied or else no update operations will take place. There are no data dependent error conditions defined after the prerequisites have been met.
-
prepared by Miloslav Nic
- the founder of Zvon.org and Law-Ref.org
- the head of B.Sc. program Informatics and chemistry [in Czech]
- the founder of Lidem.org - Volby 2006 - parliamentary elections in the Czech Republic [in Czech]
- the chief consultant of the publishing house ICT Press
- and Pavel Srb, a student of B.Sc. program Informatics and chemistry