RFC 1996: A Mechanism for Prompt Notification of Zone Changes (DNS NOTIFY)

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…

Read RFC 1996 on the RFC Editor

Outgoing relationships (2 related RFCs)

Updates, Informative reference — RFC 1035: Domain names - implementation and specification
Informative reference — RFC 1995: Incremental Zone Transfer in DNS

Incoming relationships (16 related RFCs)

Normatively referenced by — RFC 9499: DNS Terminology
Normatively referenced by — RFC 5936: DNS Zone Transfer Protocol (AXFR)
Normatively referenced by — RFC 7719: DNS Terminology
Normatively referenced by — RFC 9103: DNS Zone Transfer over TLS
Normatively referenced by — RFC 9526: Simple Provisioning of Public Names for Residential Networks
Normatively referenced by — RFC 9859: Generalized DNS Notifications
Normatively referenced by — RFC 4450: Getting Rid of the Cruft: Report from an Experiment in Identifying and Reclassifying Obsolete Standards Documents
Informatively referenced by — RFC 1995: Incremental Zone Transfer in DNS
Informatively referenced by — RFC 6781: DNSSEC Operational Practices, Version 2
Informatively referenced by — RFC 4704: The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) Client Fully Qualified Domain Name (FQDN) Option
Informatively referenced by — RFC 6810: The Resource Public Key Infrastructure (RPKI) to Router Protocol
Informatively referenced by — RFC 4641: DNSSEC Operational Practices
Informatively referenced by — RFC 4702: The Dynamic Host Configuration Protocol (DHCP) Client Fully Qualified Domain Name (FQDN) Option
Informatively referenced by — RFC 6195: Domain Name System (DNS) IANA Considerations
Informatively referenced by — RFC 8210: The Resource Public Key Infrastructure (RPKI) to Router Protocol, Version 1
Informatively referenced by — RFC 2010: Operational Criteria for Root Name Servers