Generalized DNS Notifications
RFC 9859
Revision differences
Document history
| Date | By | Action |
|---|---|---|
| 2025-09-30 | (System) | IANA registries were updated to include RFC9859 |
| 2025-09-28 | (System) | Received changes through RFC Editor sync (created document RFC 9859, created became rfc relationship between draft-ietf-dnsop-generalized-notify and RFC 9859, set abstract to 'This … Received changes through RFC Editor sync (created document RFC 9859, created became rfc relationship between draft-ietf-dnsop-generalized-notify and RFC 9859, set abstract to 'This document generalizes and extends the use of DNS NOTIFY (RFC 1996) beyond conventional zone transfer hints to allow other types of actions that were previously lacking a trigger mechanism to be triggered via the DNS. Notifications merely nudge the receiver to initiate a predefined action promptly (instead of on a schedule); they do not alter the action itself (including any security checks it might employ). To enable this functionality, a method for discovering the receiver endpoint for such notification messages is introduced, via the new DSYNC record type. Notification types are recorded in a new registry, with initial support for parental NS and DS record updates including DNSSEC bootstrapping.', set pages to 16, set standardization level to Proposed Standard, added RFC published event at 2025-09-28) |
| 2025-09-28 | (System) | RFC published |