HTTP/2 200 date: Mon, 14 Jul 2025 20:31:31 GMT content-type: application/xml cache-control: public, max-age=3600 cross-origin-opener-policy: same-origin expires: Mon, 14 Jul 2025 21:31:31 GMT referrer-policy: same-origin vary: Cookie, origin, Accept-Encoding x-content-type-options: nosniff x-frame-options: DENY x-resolution-methods: manual;auto;fallback x-resolution-outcomes: ;RfcAdapter: using docid IETF RFC 8765 -> using query @.type == "IETF" && @.primary == true && @.id == "RFC 8765" -> 1 found,; last-modified: Mon, 14 Jul 2025 20:31:30 GMT cf-cache-status: MISS server: cloudflare cf-ray: 95f3c8b5c8eac1b5-BLR content-encoding: gzip alt-svc: h3=":443"; ma=86400 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.