RFC 1996: A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)
In plain English — editorial summary, not part of the RFC
This memo describes the NOTIFY opcode for DNS, by which a master server advises a set of slave servers that the master's data has been changed and that a query should be initiated to discover the new data. [STANDARDS-TRACK]
Document record
- Document ID
- RFC1996
- Published
- August 1996
- Authors
- P. Vixie
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 7
- Also known as
- —
- Updates:
- RFC 1035
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 1995Incremental Zone Transfer in DNSUpdated
August 1996
- RFC 1982Serial Number ArithmeticCurrent
August 1996
- RFC 1886DNS Extensions to support IP version 6Obsoleted
December 1995
- RFC 2181Clarifications to the DNS SpecificationUpdated
July 1997
- RFC 2182Selection and Operation of Secondary DNS ServersCurrent
July 1997
- RFC 2606Reserved Top Level DNS NamesUpdated
June 1999
- RFC 2845Secret Key Transaction Authentication for DNS (TSIG)Obsoleted
May 2000
- RFC 3090DNS Security Extension Clarification on Zone StatusObsoleted
March 2001
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?