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.

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.

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).