RFC 2782: A DNS RR for specifying the location of services (DNS SRV)
In plain English — editorial summary, not part of the RFC
This document describes a DNS RR which specifies the location of the server(s) for a specific protocol and domain. [STANDARDS-TRACK]
Document record
- Document ID
- RFC2782
- Published
- February 2000
- Authors
- A. Gulbrandsen; P. Vixie; L. Esibov
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 12
- Also known as
- —
- Obsoletes:
- RFC 2052
Topics
Referenced by
2 later RFCs formally update or obsolete part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 3123A DNS RR Type for Lists of Address Prefixes (APL RR)Current
June 2001
- RFC 3597Handling of Unknown DNS Resource Record (RR) TypesUpdated
September 2003
- RFC 3402Dynamic Delegation Discovery System (DDDS) Part Two: The AlgorithmCurrent
October 2002
- RFC 3403Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) DatabaseCurrent
October 2002
- RFC 3404Dynamic Delegation Discovery System (DDDS) Part Four: The Uniform Resource Identifiers (URI)Current
October 2002
- RFC 3832Remote Service Discovery in the Service Location Protocol (SLP) via DNS SRVUpdated
July 2004
- RFC 2672Non-Terminal DNS Name RedirectionObsoleted
August 1999
- RFC 2671Extension Mechanisms for DNS (EDNS0)Obsoleted
August 1999
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?