Datagram boundaries survive delivery, but missing, repeated or reordered messages need application-defined handling.

UDP preserves datagrams; recovery and timing belong to the application

UDP carries discrete datagrams between transport endpoints. Its eight-byte header contains source port, destination port, length, and checksum fields. The protocol does not add TCP’s reliable ordered byte stream or its congestion-control behavior. This gives applications room to choose their own delivery policy, but it does not promise lower latency for every workload. A missing datagram can be more costly than a handshake when the application needs its contents. ...

November 11, 2026 · 5 min · XB Field Notes
An OPT record permits larger UDP answers, while server limits and network delivery still constrain the exchange.

EDNS advertises UDP capacity without guaranteeing path delivery

EDNS extends DNS through an OPT pseudo-record. Among other information, a request can advertise the UDP payload size its sender is prepared to receive. This allows answers beyond the traditional 512-byte DNS limit. It is an advertisement within a DNS exchange, not a network path-MTU discovery protocol or a promise that every intervening device will deliver a datagram of that size. ...

October 28, 2026 · 6 min · XB Field Notes