What is UDP?

User Datagram Protocol (UDP) is a connectionless transport-layer protocol that sends packets without establishing a session, confirming delivery, or guaranteeing order. Its minimal overhead makes it the default choice for latency-sensitive traffic such as DNS lookups, VoIP, and streaming media – and, in Versa deployments, SD-WAN tunnel encapsulation and SLA probing.

Key takeaways

• UDP sends packets without a handshake, acknowledgments, or retransmission.
• Its 8-byte header keeps overhead minimal for latency-sensitive traffic.
• Applications above UDP must handle reliability and ordering themselves.
• DNS, NTP, VoIP, and streaming media all commonly run over UDP transport.
• Versa’s SD-WAN overlay and IPsec IKE negotiation both run over UDP.

On this page: Why it matters · How it works · Types · UDP & Versa · FAQ

Why is UDP important?

UDP matters because many network functions cannot tolerate the setup overhead TCP requires. DNS resolution, real-time voice and video, and network telemetry favor UDP’s fire-and-forget model: with no handshake or retransmission, it delivers packets with minimal delay – critical where a late packet is worse than a lost one.

It is also foundational: DNS runs over UDP port 53, NTP over port 123, and SNMP traps over port 162. In SD-WAN and VPN architectures, UDP’s simplicity makes it the preferred encapsulation layer for tunneled traffic – VXLAN and IPsec IKE ride on UDP because it traverses NAT and firewalls more predictably than raw IP. Firewall rules must open specific UDP ports for DNS and VoIP to work.

What is UDP?

UDP is one of the two core transport-layer protocols in the Internet Protocol suite, alongside TCP. Defined in 1980, it takes data from an application, wraps it in a UDP header, and hands it to IP for delivery. The header carries four fields – source port, destination port, length, and an optional checksum – adding only 8 bytes of overhead.

UDP is connectionless: no handshake before data flows, no acknowledgment a packet arrived, and no guarantee packets arrive in order, or at all. Applications needing reliability must implement it themselves, or accept that loss is tolerable – a deliberate tradeoff that skips the state and retransmission logic TCP requires, giving UDP the lower latency that one-to-many traffic needs.

Types of UDP

UDP has no protocol versions, but it supports a few delivery modes and one notable variant. Unicast is the default: one sender, one receiver, used by DNS queries and most application traffic. Multicast reaches a group of subscribed receivers at once, while broadcast sends a datagram to every host on a subnet, as with DHCP discovery.

Checksum handling also differs by IP version: IPv4 treats it as optional; IPv6 makes it mandatory, since IPv6 dropped the IP-layer header checksum IPv4 provided. A separate variant, UDP-Lite (RFC 3828), lets the checksum cover only part of the payload – useful for codecs that would rather take a corrupted packet than none at all.

UDP & Versa

UDP carries much of the control and data traffic across a Versa deployment. The SD-WAN overlay encapsulates branch, hub, and Controller traffic in VXLAN over UDP port 4790. IPsec IKE negotiation – the control channel for every encrypted tunnel – runs over UDP ports 500 and 4500.

Management-plane services depend on UDP too: DNS lookups use port 53, NTP/Chrony sync uses port 123, and SNMP traps and syslog travel over ports 162 and 514. VOS device alarms can stream to Director over UDP via ALARM_PROTOCOL=udp. Versa’s Application Delivery Controller also load-balances UDP connections directly, useful for log export functionality (LEF) traffic. Because so many services are UDP-based, firewall requirements list which UDP ports must stay open.

Frequently asked questions

What is the difference between UDP and TCP?

UDP sends packets without a handshake, acknowledgment, or guaranteed order, while TCP establishes a connection, confirms receipt, and retransmits lost data. TCP suits file transfers and web pages; UDP suits real-time voice, video, and DNS lookups, where speed matters more than perfect delivery.

Why do DNS and VoIP use UDP instead of TCP?

Both need fast exchanges: a DNS query and its retried follow-up are still faster than a full TCP handshake, and VoIP would rather skip a lost audio packet than pause to retransmit it. UDP’s connectionless model avoids that overhead entirely.

Is UDP reliable?

Not on its own – UDP does not acknowledge packets, retransmit losses, or guarantee ordering. Reliability, when needed, is built into the application above it, as DNS does with retries, or accepted as a tradeoff for lower latency, as VoIP does.

What ports does UDP use?

UDP addresses traffic with 16-bit port numbers, the same range TCP uses, from 0 to 65535. Well-known UDP ports include port 53 for DNS, port 123 for NTP, 161 and 162 for SNMP, 500 and 4500 for IPsec IKE, 4789 for VXLAN (the IANA assignment), and 4790 for the VXLAN encapsulation Versa’s SD-WAN overlay uses.

Why does Versa SD-WAN use UDP for its overlay traffic?

UDP’s minimal header and connectionless design let SD-WAN encapsulate already-reliable application traffic in VXLAN over UDP without adding a second layer of handshakes and retransmissions. It also traverses NAT and firewalls more predictably than raw IP protocols, which matters for tunnels crossing the public internet.

More on UDP

If you want to learn more, these are sources we trust.

Related terms

If you’re reading about UDP, these are worth looking at next.