SRV record

Using SRV (Service ) resource records can be propagated by DNS, the IP -based services ( Services) in a domain are available (eg, company ). For each service further information is provided, such as the server name that provides this service.

A service is identified by the name and appended with a point protocol. Two components, a " _ " prefix to prevent confusion with another domain name.


Example 3600 IN SRV 0 389 10 A client can determine by DNS, that in the DNS domain, the LDAP server ldap01 exists, is reachable via TCP port 389 in this example.


SRV RRs are often used by Microsoft Windows 2000 clients to determine the appropriate domain controller for a service they need.

Next SRV records are common in following standardized protocols:

  • XMPP ( Jabber)
  • SIP
  • LDAP
  • Kerberos
  • Teamspeak3 (since client version 3.0.8 ) TSDNS, its own protocol, in which simply sent to resolve the name of the domain name by TCP and returned (if no SRV RR is present, port 41144 of the A -RR used )