2. Update Message Format (original) (raw)

Connected: An Internet Encyclopedia
2. Update Message Format

Up: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 2136

Prev: 1.3. New Assigned Numbers
Next: 2.1. Transport Issues

2. Update Message Format

2. Update Message Format

The DNS Message Format is defined by [RFC1035 4.1]. Some extensions are necessary (for example, more error codes are possible under UPDATE than under QUERY) and some fields must be overloaded (see description of CLASS fields below).

The overall format of an UPDATE message is, following [ibid]:

  +---------------------+
  |        Header       |
  +---------------------+
  |         Zone        | specifies the zone to be updated
  +---------------------+
  |     Prerequisite    | RRs or RRsets which must (not) preexist
  +---------------------+
  |        Update       | RRs or RRsets to be added or deleted
  +---------------------+
  |   Additional Data   | additional data
  +---------------------+

The Header Section specifies that this message is an UPDATE, and describes the size of the other sections. The Zone Section names the zone that is to be updated by this message. The Prerequisite Section specifies the starting invariants (in terms of zone content) required for this update. The Update Section contains the edits to be made, and the Additional Data Section contains data which may be necessary to complete, but is not part of, this update.

• 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

Next: 2.1. Transport Issues

Connected: An Internet Encyclopedia
2. Update Message Format