RFC 2136 (original) (raw)
Connected: An Internet Encyclopedia
RFC 2136
Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Next: 1. Definitions
RFC 2136
RFC 2136
Network Working Group
Request for Comments: 2136
Updates: 1035
Category: Standards Track
P. Vixie, Editor
ISC
S. Thomson
Bellcore
Y. Rekhter
Cisco
J. Bound
DEC
April 1997
Dynamic Updates in the Domain Name System (DNS UPDATE)
Status of this Memo
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.
Table of Contents
- 1. Definitions
- 2. Update Message Format
- 2.1. Transport Issues
- 2.2. Message Header
- 2.3. Zone Section
- 2.4. Prerequisite Section
* 2.4.1. RRset Exists (Value Independent)
* 2.4.2. RRset Exists (Value Dependent)
* 2.4.3. RRset Does Not Exist
* 2.4.4. Name Is In Use
* 2.4.5. Name Is Not In Use - 2.5. Update Section
* 2.5.1. Add To An RRset
* 2.5.2. Delete An RRset
* 2.5.3. Delete All RRsets From A Name
* 2.5.4. Delete An RR From An RRset - 2.6. Additional Data Section
- 3. Server Behavior
- 4. Requestor Behaviour
- 5. Duplicate Detection, Ordering and Mutual Exclusion
- 6. Forwarding
- 7. Design, Implementation, Operation, and Protocol Notes
- 8. Security Considerations
- Acknowledgements
- References
- Authors' Addresses
- Original text document
- Complete HTML RFC (TAR, TGZ, or ZIP format)
Next: 1. Definitions
Connected: An Internet Encyclopedia
RFC 2136