RFC 8765: DNS Push Notifications
In plain English — editorial summary, not part of the RFC
The Domain Name System (DNS) was designed to return matching records efficiently for queries for data that are relatively static. When those records change frequently, DNS is still efficient at returning the updated results when polled, as long as the polling rate is not too high. But, there exists no mechanism for a client to be asynchronously notified when these changes occur. This document defines a mechanism for a client to be notified of such changes to DNS records, called DNS Push Notifications.
Document record
- Document ID
- RFC8765
- Published
- June 2020
- Authors
- T. Pusateri; S. Cheshire
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 32
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8599Push Notification with the Session Initiation Protocol (SIP)Current
May 2019
- RFC 8291Message Encryption for Web PushCurrent
November 2017
- RFC 8932Recommendations for DNS Privacy Service OperatorsCurrent
October 2020
- RFC 9076DNS Privacy ConsiderationsCurrent
July 2021
- RFC 9103DNS Zone Transfer over TLSCurrent
August 2021
- RFC 8310Usage Profiles for DNS over TLS and DNS over DTLSCurrent
March 2018
- RFC 9250DNS over Dedicated QUIC ConnectionsCurrent
May 2022
- RFC 8222Selecting Labels for Use with Conventional DNS and Other Resolution Systems in DNS-Based Service DiscoveryCurrent
September 2017
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?