An SRV record (service record) is a DNS record that indicates on which server and port a specific service can be found, such as VoIP telephony, Microsoft Teams, or a chat service. Unlike an A or CNAME record, an SRV record doesn’t just point to a server, it also contains priority, weight, and port number. Below you’ll read when you need an SRV record and how to set one up yourself.
What exactly is an SRV record?
An SRV record tells systems which server is responsible for a particular service within your domain, and on which port that service can be reached. Think of the difference with an MX record: an MX record only handles email, but an SRV record can be used for all kinds of services, such as internet telephony (SIP), instant messaging (XMPP), or Microsoft services like Teams and Autodiscover.
Without an SRV record, you’d have to manually enter server names and ports in each application. With an SRV record, applications can automatically look up this information via DNS, making configuration much simpler.
When do you need an SRV record?
You’ll mainly come across an SRV record with:
- VoIP telephony: SIP providers use SRV records to link phone systems to your domain.
- Microsoft Teams and Skype for Business: for automatic discovery of services within your organization.
- XMPP chat services: to locate chat servers for a domain.
- Autodiscover for Exchange/Office 365: so Outlook automatically finds the correct settings.
For regular web hosting or standard business email via IMAP/SMTP, you generally don’t need an SRV record; A, MX, and TXT records are sufficient in those cases. An SRV record mainly becomes relevant once a software provider explicitly requires it.
Structure of an SRV record
An SRV record consists of several components that together determine how and where a service can be reached:
- Service and protocol: for example _sip._tcp, this indicates which service is involved.
- Priority: a lower number means a higher preference when multiple servers are available.
- Weight: determines the distribution of traffic between servers with the same priority.
- Port: the port number on which the service runs.
- Target: the hostname of the server that provides the service.
An example looks like this: _sip._tcp.example.com. 3600 IN SRV 10 60 5060 sipserver.example.com. Here, 10 is the priority, 60 the weight, 5060 the port, and sipserver.example.com the target.
Setting up an SRV record: step by step
Gather the correct information
Ask the service you want to connect for the exact service name, protocol, priority, weight, port, and target server.
Open your DNS management
Log in to your domain management or hosting panel, such as Plesk, and go to the DNS settings screen for the relevant domain.
Add a new SRV record
Select the SRV record type and enter the service, protocol, priority, weight, port, and target exactly as specified by the provider.
Save and wait for propagation
After saving, it may take some time before the change is visible everywhere, depending on the TTL value of the record.
Test the connection
Use a DNS lookup tool to check that the SRV record is displayed correctly, then test whether the connected service works properly.
Not sure about DNS management in general, for example when setting up A, MX, or TXT records alongside your SRV record? Check out the explanation of domain names and DNS management or consult the knowledge base for more background articles.
Frequently asked questions
Can I set up multiple SRV records for the same service?
Yes, that’s possible. By adding multiple records with different priority and weight, you arrange failover and load balancing between servers.
Does an SRV record work even if the service isn’t active?
No, the record only points the way to a server and port. If the service isn’t running there, the connection won’t work, even if the DNS record is set up correctly.
Does an SRV record affect my website or email?
Not directly. An SRV record is separate from your regular website and email settings, unless a specific service explicitly requires it.
How long does it take before an SRV record becomes active?
This depends on the TTL value you set. A lower TTL results in faster propagation but requires more DNS traffic.
Conclusion
An SRV record is a specific type of DNS record that you mainly need for services such as VoIP, Teams, or chat servers. By correctly filling in service, priority, weight, port, and target, you ensure that applications automatically find the correct server. For standard web hosting and email it’s usually not necessary, but as soon as a provider asks for it, follow the step-by-step plan above.