How to Add SRV Records

SRV are ‘service’ type records added in dns zone files. These are added to indicate a certain kind of service runs on a specific port, on a specific domain/subdomain. Many control panel, will give clear distinction to make you select the following items in a srv record:

  1. Protocol Type (TCP/UDP)
  2. Weight
  3. Port
  4. Target Host

Now, if by any chance, you are doing it in a panel like Cyberpanel, or some other zone files, it is highly likely you will have a way to distinct any of these. This simple How to, is for them specially.

If for example, your domain is ‘’, and you are trying to add something like with the following details:

Protocol: TCP
Weight: 0
Port: 443
Target Host:

Let’s start with is going to be your ‘name’ field. Usually you would use ‘autodiscover’ as the name field, but in this case, you would have to use it with the protocol with a underscore and a dot (._) in front as following:


Next, you enter TTL, Prioriy as you would also do. But at the end, you have 3 more fields to enter, but you have one content/value section in your zone. For the SRV records, we fill it like the following:

weight port target_host

It means, we first give the weight, then a space, then the port, then a space, then the target hostname and then a dot to end the section. In our case, it would be:

0 443

So the whole record going to be as following: (expects priority is 10)

autodiscover._tcp 3600 IN SRV 10 0 443

Troubleshoot: Server IP address could not be found

I had a client ticket today, with the following screenshot:

The error says, ‘server IP address could not be found’. This type of error means there is a DNS resolution error. There could be 3 possibilities:

  1. Client hasn’t updated the dns nameservers for the domain
  2. Host’s DNS server is down.
  3. Client’s DNS resolver isn’t working.

To check if the client has updated the proper dns nameservers, you can use It will also tell you if the host DNS is down or not. If both are ok, you should check if you are able to load other domains using your Internet, if not, it has things to do with the local DNS resolver of your desktop or the ISP. In my case, it was client who failed to update the nameservers of the domain. All that was required to update the nameservers with the server ones.