SRV record

Last updated

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.

Contents

Record format

A SRV record has the form:

_service._proto.name. ttl IN 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.86400INSRV055060sipserver.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. [1]

Provisioning for high service availability

The priority field determines the precedence of the 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.86400INSRV10605060bigbox.example.com._sip._tcp.example.com.86400INSRV10205060smallbox1.example.com._sip._tcp.example.com.86400INSRV10205060smallbox2.example.com._sip._tcp.example.com.86400INSRV2005060backupbox.example.com.

The first three 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 three weight values is 100, so bigbox.example.com will be used 60% of the time. The two hosts, smallbox1 and smallbox2 will be used for 40% of requests total, with half of them sent to smallbox1, and the other half to smallbox2. 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 three 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. The current load of servers is not taken into account unless TTL values are low enough (around a minute or lower) that the priority (or weight) values can be quickly updated.

Usage

SRV records are common in conjunction with the following standardized communications protocols:[ clarification needed ]

In Microsoft Windows 2000 clients query for SRV records to determine 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. [21] In Microsoft Windows networks domain controllers register their network service types for Active Directory in the DNS.

An older version of the Internet Draft for OpenPGP Web Key Directory uses SRV records for discovering OpenPGP keys through web servers. [22] Usages of SRV records are no longer part of the Internet Draft in later versions. [23]

A registry of service names for SRV records & protocols is maintained by the Internet Assigned Numbers Authority (IANA) as defined in RFC 6335. [24]

See also

Related Research Articles

The Domain Name System (DNS) is a hierarchical and distributed name service that provides a naming system for computers, services, and other resources on the Internet or other Internet Protocol (IP) networks. It associates various information with domain names assigned to each of the associated entities. Most prominently, it translates readily memorized domain names to the numerical IP addresses needed for locating and identifying computer services and devices with the underlying network protocols. The Domain Name System has been an essential component of the functionality of the Internet since 1985.

<span class="mw-page-title-main">HTTP</span> Application protocol for distributed, collaborative, hypermedia information systems

HTTP is an application layer protocol in the Internet protocol suite model for distributed, collaborative, hypermedia information systems. HTTP is the foundation of data communication for the World Wide Web, where hypertext documents include hyperlinks to other resources that the user can easily access, for example by a mouse click or by tapping the screen in a web browser.

The Session Initiation Protocol (SIP) is a signaling protocol used for initiating, maintaining, and terminating communication sessions that include voice, video and messaging applications. SIP is used in Internet telephony, in private IP telephone systems, as well as mobile phone calling over LTE (VoLTE).

Time to live (TTL) or hop limit is a mechanism which limits the lifespan or lifetime of data in a computer or network. TTL may be implemented as a counter or timestamp attached to or embedded in the data. Once the prescribed event count or timespan has elapsed, data is discarded or revalidated. In computer networking, TTL prevents a data packet from circulating indefinitely. In computing applications, TTL is commonly used to improve the performance and manage the caching of data.

A name server is a computer application that implements a network service for providing responses to queries against a directory service. It translates an often humanly meaningful, text-based identifier to a system-internal, often numeric identification or addressing component. This service is performed by the server in response to a service protocol request.

A mail exchanger record specifies the mail server responsible for accepting email messages on behalf of a domain name. It is a resource record in the Domain Name System (DNS). It is possible to configure several MX records, typically pointing to an array of mail servers for load balancing and redundancy.

An application layer is an abstraction layer that specifies the shared communication protocols and interface methods used by hosts in a communications network. An application layer abstraction is specified in both the Internet Protocol Suite (TCP/IP) and the OSI model. Although both models use the same term for their respective highest-level layer, the detailed definitions and purposes are different.

<span class="mw-page-title-main">XMPP</span> Communications protocol for message-oriented middleware

Extensible Messaging and Presence Protocol is an open communication protocol designed for instant messaging (IM), presence information, and contact list maintenance. Based on XML, it enables the near-real-time exchange of structured data between two or more network entities. Designed to be extensible, the protocol offers a multitude of applications beyond traditional IM in the broader realm of message-oriented middleware, including signalling for VoIP, video, file transfer, gaming and other uses.

Zero-configuration networking (zeroconf) is a set of technologies that automatically creates a usable computer network based on the Internet Protocol Suite (TCP/IP) when computers or network peripherals are interconnected. It does not require manual operator intervention or special configuration servers. Without zeroconf, a network administrator must set up network services, such as Dynamic Host Configuration Protocol (DHCP) and Domain Name System (DNS), or configure each computer's network settings manually.

In computer networking, a hostname is a label that is assigned to a device connected to a computer network and that is used to identify the device in various forms of electronic communication, such as the World Wide Web. Hostnames may be simple names consisting of a single word or phrase, or they may be structured. Each hostname usually has at least one numeric network address associated with it for routing packets for performance and other reasons.

DNS zone transfer, also sometimes known by the inducing DNS query type AXFR, is a type of DNS transaction. It is one of the many mechanisms available for administrators to replicate DNS databases across a set of DNS servers.

A Name Authority Pointer (NAPTR) is a type of resource record in the Domain Name System of the Internet.

Multicast DNS (mDNS) is a computer networking protocol that resolves hostnames to IP addresses within small networks that do not include a local name server. It is a zero-configuration service, using essentially the same programming interfaces, packet formats and operating semantics as unicast Domain Name System (DNS). It was designed to work as either a stand-alone protocol or compatible with standard DNS servers. It uses IP multicast User Datagram Protocol (UDP) packets and is implemented by the Apple Bonjour and open-source Avahi software packages, included in most Linux distributions. Although the Windows 10 implementation was limited to discovering networked printers, subsequent releases resolved hostnames as well. mDNS can work in conjunction with DNS Service Discovery (DNS-SD), a companion zero-configuration networking technique specified separately in RFC 6763.

In computer networking, a port or port number is a number assigned to uniquely identify a connection endpoint and to direct data to a specific service. At the software level, within an operating system, a port is a logical construct that identifies a specific process or a type of network service. A port at the software level is identified for each transport protocol and address combination by the port number assigned to it. The most common transport protocols that use port numbers are the Transmission Control Protocol (TCP) and the User Datagram Protocol (UDP); those port numbers are 16-bit unsigned numbers.

An IPv6 transition mechanism is a technology that facilitates the transitioning of the Internet from the Internet Protocol version 4 (IPv4) infrastructure in use since 1983 to the successor addressing and routing system of Internet Protocol Version 6 (IPv6). As IPv4 and IPv6 networks are not directly interoperable, transition technologies are designed to permit hosts on either network type to communicate with any other host.

PKI Resource Query Protocol (PRQP) is an Internet protocol used for obtaining information about services associated with an X.509 Certificate Authority. It is described by RFC 7030 published on October 23, 2013. PRQP aims to improve Interoperability and Usabilities issues among PKIs, helping finding services and data repositories associated with a CA. Messages communicated via PRQP are encoded in ASN.1 and are usually communicated over HTTP.

DNS-based Authentication of Named Entities (DANE) is an Internet security protocol to allow X.509 digital certificates, commonly used for Transport Layer Security (TLS), to be bound to domain names using Domain Name System Security Extensions (DNSSEC).

<span class="mw-page-title-main">Well-known URI</span>

A well-known URI is a Uniform Resource Identifier for URL path prefixes that start with /.well-known/. They are implemented in webservers so that requests to the servers for well-known services or information are available at URLs consistent well-known locations across servers.

In the Domain Name System, a Uniform Resource Identifier (URI) record is a means for publishing mappings from hostnames to URIs.

References

  1. ↑ Gulbrandsen, A.; Vixie, P.; Esibov, L. (February 2000). "The format of the SRV RR". A DNS RR for specifying the location of services (DNS SRV). doi: 10.17487/RFC2782 . RFC 2782 . Retrieved 3 December 2021. There MUST be one or more address records for this name, the name MUST NOT be an alias (in the sense of RFC 1034 or RFC 2181).
  2. ↑ "DNS SRV record support in apt". Debian. 4 May 2018. Archived from the original on 17 November 2019. Retrieved 17 November 2019.
  3. ↑ "RFC6764: Locating Services for Calendaring Extensions to WebDAV (CalDAV) and vCard Extensions to WebDAV (CardDAV)".
  4. ↑ "Looking up Monitors through DNS – Ceph Documentation". Ceph Documentation. Archived from the original on 5 December 2017. Retrieved 4 December 2017.
  5. ↑ "Version 1.1.62 - Factorio Forums". Factorio Forum. Archived from the original on 16 September 2022. Retrieved 16 September 2022.
  6. ↑ "Version 1.1.67 - Factorio Forums". Factorio Forum. Archived from the original on 20 August 2022. Retrieved 16 September 2022.
  7. ↑ "Add SRV Record support - Page 4 - Factorio Forums". Factorio Forum. Archived from the original on 16 September 2022. Retrieved 16 September 2022.
  8. ↑ "Hostnames for the Master and Slave KDCs". Massachusetts Institute of Technology. Archived from the original on 21 October 2012. Retrieved 23 May 2012.
  9. ↑ Zeilenga, K. (April 2001). OpenLDAP Root Service - An experimental LDAP referral service. IETF. doi: 10.17487/RFC3088 . RFC 3088. Archived from the original on 16 January 2020. Retrieved 5 July 2020.
  10. ↑ Daboo, C. (March 2011). Use of SRV Records for Locating Email Submission/Access Services. IETF. doi: 10.17487/RFC6186 . RFC 6186. Archived from the original on 17 April 2013. Retrieved 17 April 2013.
  11. ↑ "Federation API". Matrix.org. Archived from the original on 5 July 2020. Retrieved 5 January 2018.
  12. ↑ "Java Edition 1.3.1". Minecraft Wiki. Retrieved 24 September 2023.
  13. ↑ "MongoDB Connection String URI Format". MongoDB. Archived from the original on 10 December 2022. Retrieved 14 December 2022.
  14. ↑ "Add DNS SRV record support - mumble-voip/mumble". GitHub. Archived from the original on 5 July 2020. Retrieved 5 July 2020.
  15. ↑ "Baraza - Userguide". Archived from the original on 22 August 2008.
  16. ↑ "Puppet Docs: Scaling Puppet with compile masters, Using DNS SRV Records". Puppet Labs. Archived from the original on 11 October 2019. Retrieved 17 December 2019.
  17. ↑ "Server DNS Records". Rust Wiki. Retrieved 6 November 2024.
  18. ↑ "[Suggestion] TS DNS". Teamspeak Forum . Archived from the original on 14 November 2016. Retrieved 25 October 2013.
  19. ↑ "TeamSpeak 3 Client Version 3.0.8 Released". Teamspeak Forum . Archived from the original on 27 September 2016. Retrieved 5 July 2020.
  20. ↑ "XEP-0156: Discovering Alternative XMPP Connection Methods". XMPP.org . Archived from the original on 7 May 2012. Retrieved 23 May 2012.
  21. ↑ "A new feature is available that enables Outlook 2007 to use DNS Service Location (SRV) records to locate the Exchange Autodiscover service". Microsoft Support . 13 May 2010. Archived from the original on 20 April 2012. Retrieved 23 May 2012.
  22. ↑ Koch, Werner. "OpenPGP Web Key Directory draft-koch-openpgp-webkey-service-06". IETF Datatracker. Internet Engineering Task Force. Retrieved 5 June 2021.
  23. ↑ Koch, Werner. "OpenPGP Web Key Directory draft-koch-openpgp-webkey-service-12". IETF Datatracker. Internet Engineering Task Force. Retrieved 5 June 2021.
  24. ↑ Cotton, M.; Eggert, L.; Touch, J.; Westerlund, M.; Cheshire, S. (August 2011). Internet Assigned Numbers Authority (IANA) Procedures for the Management of the Service Name and Transport Protocol Port Number Registry. IETF. doi: 10.17487/RFC6335 . RFC 6335. Archived from the original on 6 July 2020. Retrieved 6 July 2020.
This page is based on this Wikipedia article
Text is available under the CC BY-SA 4.0 license; additional terms may apply.
Images, videos and audio are available under their respective licenses.