An SRV record tells clients where a particular service lives: which host, which port, and in what order to try them. Its name spells out the service and protocol, as in _sip._tls.example.com.
| Type number | 33 |
| Name format | _service._protocol.domain |
| Target | A host name with A/AAAA records — not an IP, not a CNAME |
| Defined in | RFC 2782 |
Look up the SRV records of any name
One question to DNS, answered as it is. You can change the record type too.
What it does
Clients try the lowest priority first; among records of equal priority, weight shares the traffic in proportion. A target of “.” says the service is deliberately not offered at this domain.
Phone systems (SIP), chat (XMPP), game servers and some Microsoft 365 setups use SRV records. Web browsers do not.
How it is written
| Field | Meaning |
|---|---|
| Priority | Lower is tried first |
| Weight | Share among records of the same priority |
| Port | The service’s port |
| Target | The host offering it |
Examples
_sip._tls.example.com. 3600 IN SRV 10 60 5061 sip1.example.com.
_sip._tls.example.com. 3600 IN SRV 10 40 5061 sip2.example.com.
_sip._tls.example.com. 3600 IN SRV 20 0 5061 sip-backup.example.com.
SIP over TLS on port 5061: two servers sharing the load 60/40, and a backup tried only when both fail.
_xmpp-server._tcp.example.com. IN SRV 0 0 0 .
A target of “.”: this domain offers no XMPP federation.
Common mistakes
- Entering the whole name in a DNS panel that adds the domain itself, producing _sip._tls.example.com.example.com.
- A target that is a CNAME or an IP address.
What we recommend
Copy SRV records exactly as the service documents them, and check the name after saving.
Sources
Checked on 25 September 2026 against these official sources:
- RFC 2782: A DNS RR for specifying the location of services (DNS SRV) — rfc-editor.org