ObsoletedPROPOSED STANDARDIETF stream

RFC 2137: Secure Domain Name System Dynamic Update

This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 3007.

Current version: RFC 3007Secure Domain Name System (DNS) Dynamic Update

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

This memo describes how to use DNSSEC digital signatures covering requests and data to secure updates and restrict updates to those authorized to perform them as indicated by the updater's possession of cryptographic keys. [STANDARDS-TRACK]

Document record

Document ID
RFC2137
Published
April 1997
Authors
D. Eastlake 3rd
Status
PROPOSED STANDARD
Stream
IETF
Area
sec
Pages
11
Also known as
Obsoleted by:
RFC 3007
Updates:
RFC 1035

Topics

Referenced by

One later RFC formally updates or obsoletes 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/2137-secure-domain-name-system-dynamic-update