A DNS RR for specifying the location of services (DNS SRV) (RFC2782)
Original Publication Date: 2000-Feb-01
Included in the Prior Art Database: 2005-May-22
Internet Society Requests For Comment (RFCs)
A. Gulbrandsen: AUTHOR [+2]
This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain.
Network Working Group A.
Request for Comments: 2782 Troll Technologies
Obsoletes: 2052 P. Vixie
Category: Standards Track Internet Software Consortium
A DNS RR for specifying the location of services (DNS SRV)
Status of this Memo
specifies an Internet standards track protocol for the
Internet community, and requests discussion and suggestions for
improvements. Please refer to the current edition of the "Internet
Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
Copyright (C) The Internet Society (2000). All Rights Reserved.
describes a DNS RR which specifies the location of the
server(s) for a specific protocol and domain.
Overview and rationale
must either know the exact address of a server to
contact it, or broadcast a question.
The SRV RR
allows administrators to use several servers for a single
domain, to move services from host to host with little fuss, and to
designate some hosts as primary servers for a service and others as
Clients ask for
a specific service/protocol for a specific domain
(the word domain is used here in the strict RFC 1034 sense), and get
back the names of any available servers.
Note that where
this document refers to "address records", it means A
RR's, AAAA RR's, or their most modern equivalent.
Gulbrandsen, et al. Standards Track [Page 1]
RFC 2782 DNS SRV RR February 2000
The key words
"MUST", "MUST NOT", "SHOULD", "SHOULD
NOT" and "MAY"
used in this document are to be interpreted as specified in [BCP 14].
Other terms used in this document are defined in the DNS
specification, RFC 1034.
In general, it
is expected that SRV records will be used by clients
for applications where the relevant protocol specification indicates
that clients should use the SRV record. Such specification MUST
define the symbolic name to be used in the Service field of the SRV
record as described below. It...