If you cannot create an internal zone for the services domain, you can create a pinpoint subdomain zone on the internal name server. This method changes the forwarding relationship for the entire domain and has the potential to disrupt your internal DNS structure. Because it is authoritative, the internal name server does not forward queries to any other name server.

This method makes the internal name server authoritative for the services domain. If you do not already have a zone for the services domain on the internal name server, you can create one. Use an Internal Zone for a Services Domain Deploy records within a pinpoint subdomain zone on the internal name server.Deploy records within an internal zone for the services domain.If the services domain is not currently served by the internal name server, you can: However in a separate name design, a zone for the services domain might not exist on the internal name server. The internal name server must serve records for the services domain. The client queries for SRV records in the services domain. In a separate name design there are two domains, an internal domain and an external domain. Deploy SRV Records in a Separate Domain Structure You must deploy SRV records in each DNS zone for those service domains if your organization has multiple subsets of users who use different service domains. The services domain is determined as described in How the Client Discovers Available Services. The client queries name servers for records in the services domain. Review examples of SRV records to ensure a successful deployment. Understand which records you should provision on which name servers. You deploy multiple DNS SRV records in different locations on your enterprise DNS structure. Use an Internal Zone for a Services Domain.

Deploy SRV Records in a Separate Domain Structure.

Cisco jabber for windows dns srv