SRV RECORD

DNS SRV
A Domain Name Server (DNS) SRV record helps connecting to a SIP user in a similar way that an MX record helps email delivery. When you send email to "john@example.com", the MX record for example.com might tell the mail transfer agent to deliver email to a completely different machine, such as "zaphod.foobar.com". Similarly, when you want to make a SIP phone call to john@example.com, the SRV record might tell your computer that it should connect to "galaxy.starsystem.tw" to do so. Why use DNS SRV records for SIP? Dialling by domain names lets a SIP user have a single public "SIP address" which can be redirected at will to their current location. SRV records maintain stability and also opens up the possibility to use your own domain, regardless of the domain of the SIP service you are using. DNS SRV resource records indicates how to find services for various protocols.

SRV RECORD
An SRV record is intended to provide information on available services for your systems. A SRV record has a unique system for naming. The naming system is an underscore followed by the name of the service, followed by a period, and

underscore, and then the protocol, another dot, and then the name of the domain (the name of the domain you do not need to include in DNS Made Easy of course). Example: _http._tcp.example.com. would be the service record for web requests for example.com. The SRV record also has the following fields. They are: 1. Name The naming system is an underscore followed by the name of the service, followed by a period, and underscore, and then the protocol, another dot, and then the name of the domain (the name of the domain you do not need to include in DNS Made Easy of course). 2. Host The system that will receive the service. 3. Priority This acts the same way as the MX Level / preference in the MX record. The lower the number in the priority field, the more desirable the associated target. 0 is the highest priority (lowest number). 4. Weight Allows the zone administrators to distribute load to multiple targets (load balance). It is basically used to determine relative capacity and load between to SRV fields within the priority. Hits will be assigned proportionately by weight. So this will allow the administrators have a powerful and a weak server and share the appropriate loads between those systems. 0 is the lowest load. 5. Port the actual port of the service offered. Example: _http._tcp.example.com. SRV 0 0 80. www.example.com. This would make the web requests for example.com go to www.example.com.. 0 is the highest priority (lowest number) and 0 is the highest weight (lowest number). Example 1 SRV Record record for the example.com domain: Name Prio Wei P TT Ty Data / Host rity ght ort L pe

_http._tcp.exam 0 ple.com.

80

18 SR www.exampl 00 V e.com.

SRV record details:

o o o o o

Name: _http._tcp.example.com. is the host which are we are making an entry for. In the data entry screen we only enter _http._tcp (the domain name will be appended to the end) Priority: 0 the highest possible Weight: 0 no load balancing Port: 80 is the port that http will be accepted on. Host: www.example.com is the host that will receive the service. The data field of your record must end with a dot (.) to keep your domain name from being appended to the end of your record.

o o

TTL (time to live) The 1800 indicates how often (in seconds) that this record will be cached in resolving name servers. The end result of this record is that the SRV record _http._tcp.example.com will point to the system www.example.com.