SRV record

A Service record (SRV record) is a specification of data in the Domain Name System defining the location, i.e. the hostname and port number, of servers for specified services. It is defined in RFC 2782, and its type code is 33. Some Internet protocols such as the Session Initiation Protocol (SIP) and the Extensible Messaging and Presence Protocol (XMPP) often require SRV support by network elements.

Record format

A SRV record has the form:

_service._proto.name. TTL class SRV priority weight port target.

An example SRV record in textual form that might be found in a zone file might be the following:

_sip._tcp.example.com. 86400 IN SRV 0 5 5060 sipserver.example.com.

This points to a server named sipserver.example.com listening on TCP port 5060 for Session Initiation Protocol (SIP) protocol services. The priority given here is 0, and the weight is 5.

As in MX records, the target in SRV records must point to hostname with an address record (A or AAAA record). Pointing to a hostname with a CNAME record is not a valid configuration.

Provisioning for high service availability

The priority field determines the precedence of use of the record's data. Clients should use the SRV records with the lowest-numbered priority value first, and fall back to records of higher value if the connection fails. If a service has multiple SRV records with the same priority value, clients should load balance them in proportion to the values of their weight fields.

In the following example, both the priority and weight fields are used to provide a combination of load balancing and backup service.

# _service._proto.name.  TTL   class SRV priority weight port target.
_sip._tcp.example.com.   86400 IN    SRV 10       60     5060 bigbox.example.com.
_sip._tcp.example.com.   86400 IN    SRV 10       20     5060 smallbox1.example.com.
_sip._tcp.example.com.   86400 IN    SRV 10       10     5060 smallbox2.example.com.
_sip._tcp.example.com.   86400 IN    SRV 10       10     5066 smallbox2.example.com.
_sip._tcp.example.com.   86400 IN    SRV 20       0      5060 backupbox.example.com.

The first four records share a priority of 10, so the weight field's value will be used by clients to determine which server (host and port combination) to contact. The sum of all four values is 100, so bigbox.example.com will be used 60% of the time. The two hosts smallbox1 and smallbox2 will be used for 20% of requests each, with half of the requests that are sent to smallbox2 (i.e. 10% of the total requests) going to port 5060 and the remaining half to port 5066. If bigbox is unavailable, these two remaining machines will share the load equally, since they will each be selected 50% of the time.

If all four servers with priority 10 are unavailable, the record with the next lowest priority value will be chosen, which is backupbox.example.com. This might be a machine in another physical location, presumably not vulnerable to anything that would cause the first three hosts to become unavailable.

The load balancing provided by SRV records is inherently limited, since the information is essentially static. Current load of servers is not taken into account.

Retrieving an SRV record

SRV records may be queried with standard network administration tools, such as the Domain Information Groper (dig) or nslookup.

$ dig _sip._tcp.example.com SRV

$ host -t SRV _sip._tcp.example.com

$ nslookup -querytype=srv _sip._tcp.example.com

$ nslookup
> set querytype=srv
> _sip._tcp.example.com

Usage

SRV records are common in conjunction with the following standardized communications protocols:

In Microsoft Windows 2000 clients use SRV records to find the domain controller for a given service. SRV Records are also used by Outlook 2007, 2010 and Macintosh 10.6 mail to locate the Exchange Autodiscover service.[11] In Microsoft Windows networks, dynamic DNS is an integral part of Active Directory, because domain controllers register their network service types in DNS so that other computers in the Domain (or Forest) can access them.

A registry of service names used by SRV records and protocols is maintained by IANA and is defined in RFC6335.[12]

See also

References

  1. ↑ "Hostnames for the Master and Slave KDCs". Web.mit.edu. Retrieved 2012-05-23.
  2. ↑ "RFC 3088 - OpenLDAP Root Service An experimental LDAP referral service". Faqs.org. Retrieved 2012-05-23.
  3. ↑ "Libravatar wiki, running your own".
  4. ↑ Cyrus Daboo (March 2011). Use of SRV Records for Locating Email Submission/Access Services. IETF. RFC 6186. https://tools.ietf.org/html/rfc6186. Retrieved 17 April 2013.
  5. ↑ "Minecraft wiki, 1.3.1". Curse Inc.
  6. ↑ Archived August 22, 2008, at the Wayback Machine.
  7. ↑ "Puppet Docs: Using Multiple Puppet Masters, Option 4: DNS SRV Records". Puppet Labs. Retrieved 2013-12-26.
  8. ↑ "[Suggestion] TS DNS". Forum.teamspeak.com. Retrieved 2013-10-25.
  9. ↑ "TeamSpeak 3 Client Version 3.0.8 Released".
  10. ↑ "XEP-0156: Discovering Alternative XMPP Connection Methods". Xmpp.org. Retrieved 2012-05-23.
  11. ↑ "A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service". Support.microsoft.com. 2010-05-13. Retrieved 2012-05-23.
  12. ↑ "RFC 6335 - Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry". ietf.org. 2011-08-01. Retrieved 2013-01-28.
  13. ↑ "draft-sanz-whois-srv-00 - Using DNS SRV records to locate whois servers". Tools.ietf.org. 2004-04-05. Retrieved 2013-05-20.

External links

This article is issued from Wikipedia - version of the Wednesday, April 27, 2016. The text is available under the Creative Commons Attribution/Share Alike but additional terms may apply for the media files.