DNS records

SRV record

An SRV (service) record tells software which host and port run a particular service for a domain, with priorities and weights for backups and load sharing. Calendar and contacts apps, SIP phones, XMPP chat, Minecraft, Microsoft Teams and email client autoconfiguration all use SRV records.

Record typeSRV
Type number33
Used forServices
How commonCommon
Defined inRFC 2782

Format

_<service>._<protocol>.<name> <ttl> IN SRV <priority> <weight> <port> <target>
FieldWhat it meansAccepted values
Service and protocolThe name says which service and transport this is for._sip._tcp, _imaps._tcp, _minecraft._tcp, _xmpp-client._tcp.
PriorityLower is tried first, as with MX.0 to 65535.
WeightAmong targets with the same priority, the share of traffic each gets.0 to 65535. 0 means no preference.
PortThe port the service listens on.0 to 65535.
TargetThe host running the service. . means not available here.A host name with an A or AAAA record, not a CNAME.

Check an SRV record

Type or paste a record in zone-file form (name, TTL, type, value) or just its value. Each part is explained as you type.

A valid SRV record.

PartWhat it means
Name_sip._tlsA service name. Underscore names hold records for a protocol (such as _dmarc or _sip._tcp), not a website.
TTL3600Resolvers may keep this answer for 1 hour before asking again. Changes can take that long to reach everyone.
ClassINInternet. Every record you'll write uses IN.
TypeSRVWhere a service runs: host and port.
Priority100Lower is tried first, like MX priority.
Weight1Among servers with the same priority, higher weight gets a bigger share of traffic.
Port443The service listens on port 443.
Targetsipdir.online.lync.com.The host that runs the service. Must have an A or AAAA record, not a CNAME.

Examples

Microsoft Teams (SIP)

_sip._tls 3600 IN SRV 100 1 443 sipdir.online.lync.com.

One of the records Microsoft 365 asks for.

Minecraft server on a custom port

_minecraft._tcp.play 3600 IN SRV 0 5 25566 mc.example.com.

Players type play.example.com and the game finds port 25566.

Two servers sharing load

_xmpp-client._tcp 3600 IN SRV 10 60 5222 a.example.com.
_xmpp-client._tcp 3600 IN SRV 10 40 5222 b.example.com.

Same priority, so roughly 60% of clients go to a and 40% to b.

Service not offered

_imap._tcp 3600 IN SRV 0 0 0 .

Clients shouldn't try plain IMAP here.

See it on a real domain

TTL

Common mistakes

  • Leaving out the underscores or the protocol label: it's _sip._tcp, not sip.
  • Pointing the target at a CNAME or an IP address.
  • Some dashboards have separate Service, Protocol and Name fields; filling the whole name into Name as well gives _sip._tcp._sip._tcp.

At your DNS host

  • Cloudflare: separate fields for service, protocol, name, priority, weight, port and target.
  • Route 53: one value: 10 60 5060 sip.example.com.
  • GoDaddy: Service and Protocol fields take the underscore names, such as _sip and _tcp.

Questions

What's the difference between priority and weight?

Priority picks which group of servers is used first (lowest wins). Weight shares traffic within that group.

Do browsers use SRV records?

No. Websites use A, AAAA and HTTPS records. SRV is for other protocols.

This page is also available as Markdown.

Lemon Domains keeps every domain you own in one place, with expiry reminders, change monitoring and DNS editing from your AI assistant. Get started free