DNS SRV record in VCS and VCS expressway

[KRISHNA K V]

Hi All, 
As per the vcs control and expressway deployment guide i need some clarification regarding the SRV records mentioend in the document.
http://www.cisco.com/en/US/docs/telepresence/infrastructure/vcs/config_guide/X8-1/Cisco-VCS-Basic-Configuration-Control-with-Expressway-Deployment-Guide-X8-1.pdf

The fqdn of VCS Control is vcsc.internal-domain.net and vcsexpressway is vcse.example.com
Internal Dns server Domain is internal-domain.net and external dns server domain is example.com 
SIP Domain configured in VCS Control and Expressway is example.com 

SRV Record in the external dns server is as below. 
 _h323cs._tcp.example.com. 86400 IN SRV 10 10 1720 vcse.example.com.
 _h323ls._udp.example.com. 86400 IN SRV 10 10 1719 vcse.example.com.
 _h323rs._udp.example.com. 86400 IN SRV 10 10 1719 vcse.example.com.
 _sip._tcp.example.com. 86400 IN SRV 10 10 5060 vcse.example.com.
 _sip._udp.example.com. 86400 IN SRV 10 10 5060 vcse.example.com.
 _sips._tcp.example.com. 86400 IN SRV 10 10 5061 vcse.example.com.
 _turn._udp.example.com. 86400 IN SRV 10 10 3478 vcse.example.com.

 Here example.com in the _h323cs._tcp.example.com. referes to the SIP Domain. so if somebody calls the sip uri  ex90@example.com the request will be directed to the vcse.example.com

SRV record in the internal dns server is as below.  
 _h323cs._tcp.internal-domain.net. 86400 IN SRV 10 10 1720 vcsc.internal-domain.net.
 _h323ls._udp.internal-domain.net. 86400 IN SRV 10 10 1719 vcsc.internal-domain.net.
 _h323rs._udp.internal-domain.net. 86400 IN SRV 10 10 1719 vcsc.internal-domain.net.
 _sip._tcp.internal-domain.net. 86400 IN SRV 10 10 5060 vcsc.internal-domain.net.
 _sip._udp.internal-domain.net. 86400 IN SRV 10 10 5060 vcsc.internal-domain.net.
 _sips._tcp.internal-domain.net. 86400 IN SRV 10 10 5061 vcsc.internal-domain.net.

in the vcs control,  sip domain name is example.com.  so i feel the  SRV record in the internal dns server should be as follows. Please let me know if this is correct. 

_h323cs._tcp.example.com. 86400 IN SRV 10 10 1720 vcsc.internal-domain.net.
 _h323ls._udp.example.com. 86400 IN SRV 10 10 1719 vcsc.internal-domain.net.
 _h323rs._udp.example.com. 86400 IN SRV 10 10 1719 vcsc.internal-domain.net.
 _sip._tcp.example.com. 86400 IN SRV 10 10 5060 vcsc.internal-domain.net.
 _sip._udp.example.com. 86400 IN SRV 10 10 5060 vcsc.internal-domain.net.
 _sips._tcp.example.com. 86400 IN SRV 10 10 5061 vcsc.internal-domain.net.
 _turn._udp.example.com. 86400 IN SRV 10 10 3478 vcsc.internal-domain.net. 

Krishna

[Jens Didriksen]

You shouldn't need the _h323rs record for the VCS-E unless you want the external endpoints to automatically register to it.

Also, the VCS-E is the turn server, not the VCS-C, so _turn record can be removed from VCS-C, or you point it to the VCS-E instead.

/jens

Please rate replies and mark question(s) as "answered" if applicable.

[KRISHNA K V]

Hi Jens, 

Thanks for your reply. Please let me know if the SRV Record domain name  in the internal dns server as mentioned in the above example   is correct or not. 

Krishna. 

[Jens Didriksen]

Couple of things, you said "Here example.com in the _h323cs._tcp.example.com. referes to the SIP Domain. so if somebody calls the sip uri  ex90@example.com the request will be directed to the vcse.example.com" - no, it doesn't, that is referring to a H.323 call, so SIP domain configured on the VCS-E doesn't come into it.

SRV records for internal DNS server using internal-domain.net, is incorrect, unless you also use internal-domain.net for addressing and/or provisioning, in which case internal-domain.net should be added to the SIP domains the VCS-C is an authority for.

However, if you use example.com for adressing/provisioning. then your edited version is correct.

Just be aware, if you change the internal SRV records to your edited version using example.com, then this should not be visible externally, as you already have the public SRV records pointing to the VCS-E for this domain - and this in turn, should not be visible internally. So, I guess split DNS is the go, which I assume you are doing.

/jens

Please rate replies and mark question(s) as "answered" if applicable.