SRV record: Definition, Use Cases, and Examples

SRV (Service) is a DNS record that specifies hostname and port for a service. Used by XMPP, SIP, Minecraft, Kerberos, LDAP. Format: _service._proto.name TTL IN SRV priority weight port target. Example: _sip._tls.example.com. 3600 IN SRV 10 60 5061 sipserver.example.com.

Open tool →

An SRV (Service) DNS record is essential for directing traffic to specific services running on a domain. Its structure is defined by several components, each serving a distinct purpose. The format is as follows:

Here's a breakdown of each component:

• _service: This indicates the specific service you are using, such as _sip for SIP services or _xmpp for XMPP.
• _proto: This signifies the transport protocol used, typically _tcp or _udp.
• name: The domain name where the service is hosted, often ending with a domain extension (e.g., example.com).
• TTL: Time to Live, which specifies how long the record is cached by DNS resolvers.
• priority: A lower number indicates higher priority. This is used when multiple SRV records exist for the same service.
• weight: Used to distribute load between multiple servers with the same priority. Higher weights receive more traffic.
• port: The port number on which the service is running (e.g., 5061).
• target: The hostname of the server providing the service.

Understanding this structure is critical for configuring services that rely on DNS SRV records, ensuring that your applications can locate and connect to the appropriate servers.

Checking SRV records can be accomplished using various command line tools, such as dig and nslookup. Below are examples of how to utilize these tools to verify SRV records for a specific service:

Using dig

The dig command provides detailed information about DNS records. To check an SRV record, use the following syntax:

For example, to check the SRV record for a SIP service on example.com, you would run:

This command will return the SRV record details, including priority, weight, port, and target hostname.

Using nslookup

The nslookup command can also be used to query SRV records. The syntax is slightly different:

For instance, to check the same SIP service, you would execute:

Both commands will provide you with the necessary information to confirm the existence and correctness of your SRV records, helping diagnose any potential connectivity issues.

SRV records are utilized across various applications and services to facilitate efficient service discovery. Here are some common use cases:

• VoIP Services: SRV records play a crucial role in Voice over IP (VoIP) applications like SIP. They help clients discover the correct server and port for making calls.
• Instant Messaging: Services such as XMPP (Jabber) use SRV records to locate chat servers, ensuring that messages are routed correctly.
• Gaming: Multiplayer games like Minecraft utilize SRV records to direct players to game servers. This allows for easier connection without needing to specify ports manually.
• Enterprise Applications: Applications using Kerberos for authentication often rely on SRV records to find the Key Distribution Center (KDC) for secure ticket granting.
• LDAP Services: Lightweight Directory Access Protocol (LDAP) services use SRV records to locate directory servers, optimizing access to user information.

In each of these cases, SRV records streamline the connection process, allowing clients to locate services dynamically without hardcoding server details. This flexibility is particularly beneficial in environments where services may change frequently.