UpdatedPROPOSED STANDARDIETF stream

RFC 2136: Dynamic Updates in the Domain Name System (DNS UPDATE)

Still current, but amended. Parts of this document are changed or extended by RFC 3007, RFC 4033, RFC 4034, RFC 4035. Read both.

In plain English — editorial summary, not part of the RFC

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. [STANDARDS-TRACK]

Document record

Document ID
RFC2136
Published
April 1997
Authors
P. Vixie; S. Thomson; Y. Rekhter; J. Bound
Status
PROPOSED STANDARD
Stream
IETF
Area
int
Pages
26
Also known as
Updates:
RFC 1035

Topics

Referenced by

4 later RFCs formally update or obsolete part of this document.

Related documents

Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.

Also filed under

About this page

The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.

Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.

Data sources · Editorial policy · Report a correction · What is an RFC?

canonical URL: /rfc/2136-dynamic-updates-in-the-domain-name-system-dns-update