We are planning to deploy at one of our customers the Jabber client and the MRA services.
This customer has 2 Domains, Internal and External and it is not possible to add the External Domain as a Zone in the Internal DNS server.
Usually when we deployed a solution that included 2 Domain, we added the External Domain as a new Zone to the Internal DNS server and forces the Jabbers to query SRV records using the External domain, by using MSI Switch SERVICES_DOMAIN=EXTERNAL_DOMAIN.
Users will sign in with external domain or internal domain?
anyways in both cases you need to resolve _cisco-uds internally and that is where you you will stuck as you can't add the domain in DNS server.
There is a Per-domain DNS server filed under System -->DNS of expressway
So you can make a separate windows DNS server and add only the specific domain for SRV query and mentioned this under Per-Domain DNS server.
I think it will solve your purpose and will not impact for other DNS queries :-)
Please rate if it is helpful and mark as accepted solution if applicable...
Thanks for you replay.
We would like to use the External domain to sign in, since the Internal domain doesn't exist outside the organization.
The solution you offered can resolve the connectivity from outside the organisation.
But what will happen to a Jabber client (Laptop) that got registered inside the customer's LAN and moved outside the network.
I dont see how it could work, unless we will disable the UPN Discovery, and ask the customer to login using the local domain from inside his network and the external domain from outside.
unless you have a better idea :)
If you are using external domain for logging then you need to have the DNS entry internally resolving the SRV queries.
Else there is no other way.
Please refer the below link, may be you will get some idea-
Please rate if it is helpful and mark as accepted solution if applicable....
As i mentioned, It is not possible to add the external Zone in the Internal DNS servers.
So I think my options will be the following 2:
- Create one separate Zone for the VOIP services
- Using 2 different domains for sign in Internal/External