What is an SRV Record?
SRV (SeRVice) records allow flexibility and stability to services making use of them. Like a "general use" MX record, the SRV records relate to a particular service of the domain, like FTP or SIP, rather than a specific machine the way A or C-name records do.
Several programs are starting to make use of SRV records for VOIP.
A Junction Networks and OnSIP customer would create an SRV record to take the place of the domain.onsip.com address given by default. With an SRV record a user with the SIP address of:
could become just:
assuming that the user can create an SRV record for acme.com.
For Junction Networks, when setting up a SRV record, the general settings are:
Service: SIP
Protocol: UDP
Name: acme.com (your domain name goes here)
Priority:
Weight:
Port: 5060
Target: sip.onsip.com
TTL: 1 hour
In BIND, an SRV record would look like this:
_sip._udp.acme.com. 3600 IN SRV 0 0 5060 sip.onsip.com.
To test that the SRV record has been entered correctly you need to run a DIG command from a terminal window (Windows PC's don't have DIG command in their terminal window so ask someone running UNIX or Linux to carry out this part).
The following screen shot shows the command: dig _sip._udp.bytetel.com SRV (replace bytetel.com with your domain name but keep everything else there).
If everything has been set up correctly you will get a confirmation answer:
This shows that the SIP SRV record for bytetel.com points to port 5060 at sip.onsip.com.
XMPP Records
You need to add two (2) SRV records to make XMPP work. Note that the protocol is TCP and that the ports are specific to the service.
In BIND, the records look like:
_xmpp-client._tcp.acme.com. 3600 IN SRV 0 0 5222 xmpp-client.onsip.com.
_xmpp-server._tcp.acme.com. 3600 IN SRV 0 0 5269 xmpp-server.onsip.com.
You can look an example up using dig on junctionnetworks.com
dig _xmpp-client._tcp.junctionnetworks.com SRV
dig _xmpp-server._tcp.junctionnetworks.com SRV
So...
Service: XMPP-CLIENT
Protocol: TCP
Name: acme.com
Priority: 0
Weight: 0
Port: 5222
Target: xmpp-client.onsip.com
TTL: 1hour
-- and --
Service: XMPP-SERVER
Protocol: TCP
Name: acme.com
Priority: 0
Weight: 0
Port: 5269
Target: xmpp-server.onsip.com
TTL: 1hour
- Printer-friendly version
- Login or register to post comments




Can be verified in windows
The SRV entry can be verified in windows from the command prompt as follows
nslookupset type=srv
_sip._udp.bytetel.com
Also, shouldn't the BIND entry include the TTL as follows?
_sip._udp.acme.com. 3600 IN SRV 0 0 5060 sip.onsip.comYes, thank you for the
Yes, thank you for the correction.
---
Erick Johnson
Junction Networks Engineer