SRV Records are a type of DNS record that specifies a server and port for a particular service. Like the way MX records specify where mail for a domain should go, SRV records point to a specific server and port.

Some services can require an SRV record to be created for your domain name.

SRV records with various DNS hosting providers

When hosting your DNS records with various DNS hosting providers, you can manage your SRV record by logging into their control panel. 

The following syntax is commonly used by many DNS hosting providers:

  • Service: this is the symbolic service name: _sip
  • Protocol: the protocol used by service: _tls
  • Priority/Preference: number: the lower number means the higher priority.
  • Weight: this is similar to priority, as it controls the order in which multiple records are used.
  • Destination/Target: points to the destination that the record is sending the traffic to.
  • TTL: time to live value; a mechanism that limits the lifespan or lifetime of data in a computer or network. We recommend setting the value to 14400 for the SRV record.
  • Name: your domain name.

SRV Record Syntax

To find the correct SRV record, please log in to the HostPilot and navigate to Services > Domains > > Display DNS records > Show System Records:


SRV Record types

These are the types of SRV records that can be in place:

Skype for Business Federation

We need SRV records for Skype for Business Federation to work (in addition to the Extended Service Request).

e.g. SRV 0 0 5061

See the KB article What is Skype for Business Federation? for more details.

Autodiscover SRV record

In rare cases, the Autodiscover SRV record can be in place and cause incorrect Autodiscover resolution.

The parameters for an autodiscover SRV Records are:

  • Service: _autodiscover
  • Protocol: _tcp
  • Port: 443
  • Host: server name

The syntax is:

Please note that only the CNAME autodiscover record should be in place as per the following article What Is An Autodiscover Record And Why Do I Need It?

Ideally, the Autodiscover SRV record should be removed, as a temporary fix, we can use the DWORD "ExcludeSrvRecord" with value 1 as per the following article.