The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Contents
You deploy multiple DNS SRV records in different locations on your enterprise DNS structure. Understand which records you should provision on which name servers. Review examples of SRV records to ensure a successful deployment.
The client queries name servers for records in the services domain. The services domain is determined as described in How the Client Discovers Available Services.
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.
In a separate name design there are two domains, an internal domain and an external domain. The client queries for SRV records in the services domain. The internal name server must serve records for the services domain. However in a separate name design, a zone for the services domain might not exist on the internal name server.
If you do not already have a zone for the services domain on the internal name server, you can create one. This method makes the internal name server authoritative for the services domain. Because it is authoritative, the internal name server does not forward queries to any other name server.
This method changes the forwarding relationship for the entire domain and has the potential to disrupt your internal DNS structure. If you cannot create an internal zone for the services domain, you can create a pinpoint subdomain zone on the internal name server.
Support of the fixed pinpoint subdomain has been replaced in later versions of Cisco Jabber by the support of the new VoiceServicesDomain configuration key.
Set VoiceServicesDomain=cisco-uc.example.com
Create a zone on both the internal and external DNS server for cisco-uc.example.com.
You can create a pinpoint subdomain and zone on the internal name server. The pinpoint zone provides a dedicated location to serve specific records for the pinpoint subdomain. As a result, the internal name server becomes authoritative for that subdomain. The internal name server does not become authoritative for the parent domain, so the behavior of queries for records in the parent domain does not change.
The following diagram illustrates configuration created by the procedure.
In this configuration, the following SRV records are deployed with the internal DNS name server:
When the client queries the name server for SRV records, it issues additional queries if the name server does not return _cisco-uds or _cuplogin.
The additional queries check for the cisco-internal.domain-name pinpoint subdomain zone.
Understand which SRV records you should deploy and review examples of each SRV record.
Service Record | Description | ||
---|---|---|---|
_collab-edge | Provides the location of the Cisco VCS Expressway or Cisco Expressway-E server.
|
_collab-edge._tls.example.com SRV service location: priority = 3 weight = 7 port = 8443 svr hostname = vcse1.example.com _collab-edge._tls.example.com SRV service location: priority = 4 weight = 8 port = 8443 svr hostname = vcse2.example.com _collab-edge._tls.example.com SRV service location: priority = 5 weight = 0 port = 8443 svr hostname = vcse3.example.com
Service Record | Description |
---|---|
_cisco-uds | Provides the location of Cisco Unified Communications Manager version 9 and higher. In an environment with multiple Cisco Unified Communications Manager clusters, you must configure the Intercluster Lookup Service (ILS). ILS enables the client to find the user's home cluster and discover services. |
_cuplogin | Provides the location of Cisco Unified Presence. |
Note | You should use the fully qualified domain name (FQDN) as the hostname in the SRV record. |
_cisco-uds._tcp.example.com SRV service location: priority = 6 weight = 30 port = 8443 svr hostname = cucm3.example.com _cisco-uds._tcp.example.com SRV service location: priority = 2 weight = 20 port = 8443 svr hostname = cucm2.example.com _cisco-uds._tcp.example.com SRV service location: priority = 1 weight = 5 port = 8443 svr hostname = cucm1.example.com
_cuplogin._tcp.example.com SRV service location: priority = 8 weight = 50 port = 8443 svr hostname = cup3.example.com _cuplogin._tcp.example.com SRV service location: priority = 5 weight = 100 port = 8443 svr hostname = cup1.example.com _cuplogin._tcp.example.com SRV service location: priority = 7 weight = 4 port = 8443 svr hostname = cup2.example.com