SRV records seem to be an evolving standard and are intended to
replace the old A records. This means there's lots of information, but
not many examples.
On this page (http://www.menandmice.com/online_docs_and_faq/glossary/glossarytoc.htm?srv.record.htm)I
found this information:
SRV Record: Also known as a Service record. An SRV record is
intended to provide information on available services. A SRV record
has four fields and 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 four fields are.
1. Priority, just a in MX records
2. Weight, used to determine relative capacity between to SRV
fields with the priority. Hits will be assigned proportionately by
weight, allowing a powerful and a weak server to share appropriate
loads.
3. Port, the port of the service offered
4. Hostname
For Example
_http._tcp.example.com. SRV 10 5 80. www.example.com
That's useful background information, and here's the authoritative
view from Microsoft:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;q232025&
Using this as my query
(://www.google.com/search?q=draft-ietf-dnsext-rfc2782bis-00.txt&hl=en&lr=&ie=UTF-8&oe=UTF-8&safe=off)
I came up with this example. You'll need to decide if you want to use
UDP or TCP as your transport and of course fill in the correct names
for your host(s) and domain.
_im_sip._[udp|tcp].yournamehere.com. SRV 10 5 5060.
servername.yournamehere.com
The general syntax is:
_Service._Proto.Domain TTL Class SRV Priority Weight Port
Target |