Visual RFC.
ALL RFCs / RFC 1996
Read the RFC ↗
RFC 1996 / DNS ZONE NOTIFICATION

Bound retries and distinguish completion from success

05

NOTIFY uses UDP by default. Because packets can be lost, the sender keeps per-destination notification state and retries within configured limits.

RFC 1996 · § 3.4 and related clausesEXAMPLE
4 / 4
Bound retries and distinguish completion from successIf TCP is needed, for example by a firewall policy, send the request once. A stalled NOTIFY transaction must not stop either server answering ordinary DNS requests. Its reasonable timeout is an operational choice, not a new fixed protocol deadline.Per-destination retry stateMasterSecondaryTCP: send NOTIFY onceBoth servers keep answering ordinary queriesDNS service continuesTimeout after a reasonable configured intervalRFC1996 · fictional zone · simplified illustrations
04
Use TCP without blocking name service

If TCP is needed, for example by a firewall policy, send the request once. A stalled NOTIFY transaction must not stop either server answering ordinary DNS requests. Its reasonable timeout is an operational choice, not a new fixed protocol deadline.

Source for this drawing: RFC 1996 · Read RFC source: § 3.4 and related clauses ↗

Protocol participantThreat or exceptionProtocol controlSimplified drawings · precise section references
New to this? Start hereA quick picture + helpful background

A message needs an address.

Think of a packet as a small addressed envelope. Devices pass it onward; transport protocols decide what delivery promises an application gets.

Helpful first, if these ideas are unfamiliar

These pictures are analogies to help you learn. The linked RFC explains the actual rules.

Related RFCs and changes

“Updates” changes part of an earlier RFC. “Obsoletes” replaces it. This list shows selected related documents.

KEY POINT

Use UDP unless there is reason to use TCP. A UDP response must match the query ID, QNAME, source IP address and source port before it ends this retry event.

  • Use UDP unless there is reason to use TCP. A UDP response must match the query ID, QNAME, source IP address and source port before it ends this retry event.
  • UDP stops after a matching response, too many copies or a port-unreachable indication. Retry interval and retry limits should be administrator parameters; 60 seconds and five retransmissions are suggested defaults, not universal mandatory values.
  • TCP sends the NOTIFY request once and times out after a reasonable interval; both servers must continue ordinary name service while it stalls. A NOTIMP response should complete the notification transaction for that receiver, not certify refreshed data.
DETAILS

Fictional picnic.example zone and documentation-only addresses. Drawings are schematic; no DNS traffic, server configuration or zone transfer is performed.

Read the RFC section ↗

All chapters in RFC 1996

Drawing view

Scroll the drawing to see every part. Playback controls stay above it.

RFC 9700 / CHAPTERS

Chapters

For full details, tables, algorithms, and exceptions, read the original RFC.

RFC status and corrections ↗