Now Available: DNS SRV Records

After the recent upgrades of our hosting platform, this has allowed us to implement the use of DNS Service (SRV) Records. This article will explain what they are and how you can add them to your domain within the control panel for your hosting account.


What is a DNS SRV Record?

An SRV record allows end users to communicate directly with services that don’t run on “standard” ports. The best example I can think of is Team Speak which could use non standard port numbers. What SRV records do is map the domain/sub-domain to the port number.

What does an SRV Record look like?

If we keep with the Team Speak example with the domain “domain.tld”- This is the format you would generally see:

_service._protocol.name TTL class SRV priority weight port data

Let’s break this down into each section:

_service: This describes the service which the record is for, this has to be specific to the application, you must also check that the application supports SRV records. For Team Speak 3, this is _ts3

._protocol: This defines the type of port which the service is listening on – The most common is ._tcp – However, for Team Speak this is ._udp

.name: This part determines what domain or sub-domain is used. For our example it will be .ts – Notice there isn’t a dot after the ts – This means that the regular domain will be added on afterwards to create “ts.domain.tld” – If you wanted it on your regular domain you would set the .name section to .domain.tld. – The trailing dot is very important, without it you would end up with domain.tld.domain.tld.

TTL: This stands for “Time to Live” Usually the default setting for this is fine. You don’t need to worry about this too much.

CLASS: Again, this isn’t too much to worry about, most of the time this is pre-set/hidden

SRV: This basically tells the name server what type of record you are creating. This is also pre-set/hidden

Priority: This is also only used if you have multiple endpoints, like MX records, you can set which ones are “more important” than others.

Weight: This is only used if you have multiple endpoints for your application. It’s to help with balancing the load between different servers. Most of the time this can be set to “0” (zero) as it is not required.

Port: This is the port number for the application you’re using. In our example, it could be something random like 9742.

Data: This is the target, which has to be a valid A record which points to an IP address (the trailing dot at the end of the address isn’t required). You can’t directly use an IP address in this section. Find out more about custom A records here

So if we put all this together. The record looks something like this:

_ts3._udp.ts 86400 IN SRV 0 0 9742 ts.domain.tld.

Once this record has propagated you would no longer need to manually specify the port number for TeamSpeak, or provide the port number to your members.

Other examples of great uses for SRV Records are Autodiscover for Microsoft exchange and SIP/Lync

If you have any comments or questions regarding SRV Records, please use the comments section below (if not domain/account specific in which case contact support team through normal methods).


Rate this post 1 Star2 Stars3 Stars4 Stars5 Stars (No Ratings Yet)
Loading...

This entry was posted in Customer Support, Email, Headlines, Network & DNS, Tutorials. Bookmark the permalink.

Leave a Reply

Please DO NOT use this form to submit support requests, all information submitted will be PUBLICLY VISIBLE.

Required fields are marked *

Time limit is exhausted. Please reload CAPTCHA.