PINPOINT PRO OPTICS WINDOWS
Windows CLI presents two methods - either dnscmd or PowerShell commands. Once added via CLI, these SRV records are manageable with the regular tools just as any other entry.
You must not add an SRV record to a pinpoint DNS entry through the GUI, as this does not work. In order to add the SRV record itself, a CLI tool must be used. This step can be performed through the Graphical User Interface (GUI) as well, although the example below assumes that the pinpoint DNS entry has not already been created. The pinpoint DNS entry is created as any other zone, and its name must contain the entire SRV name (for example, _cisco-uds._). The _collab-edge._tls SRV record must be resolvable from the external network, and resolves to the Fully Qualified Domain Name (FQDN) of the Expressway-E server. The _cisco-uds._tcp SRV record must be only resolvable on the internal network, not from the external, and must resolve to the fully qualified domain name (FQDN) of the CUCM node(s) with User Data Services (UDS). First the pinpoint DNS zone needs to be created, then the SRV within the zone. When the authorative zone file for only exists on the external NS, a pinpoint DNS entry for _cisco-uds._tcp is required on the internal NS. You can have multiple entries for these records if the Expressway and/or the Cisco Unified Communications Manager (CUCM) is clustered. Configureįor Cisco Jabber auto-provisioning, as well as Mobile and Remote Access (MRA) service, two SRV records are involved for each domain (using as an example): Pinpoint DNS entries offer an alternative in these cases. Since this can lead to management overhead, some network administrators prefer to avoid split DNS configurations. Entries present in the external zone, but not in the internal zone must fail to resolve for internal queries. In a split DNS configuration, an internal DNS server maintains a copy of the zone with internal-specific entries and an external DNS server maintains a copy of the zone with external-specific entries. Thus, in order to provide different name resolution within the same domain to internal and external users of the domain normally, a split DNS would be used. If a Name Server is configured as authoritative or master for a domain, then queries are not forwarded for names within that domain to its forwarders, even if it can be unable to resolve a specific name. It is also a supported solution for Cisco Jabber deployment if split DNS is not available. This is a feature of the DNS system and does not rely on any mechanism in the Cisco Jabber or Cisco Expressway applications. The following image provides an example of these records: The symbol is also used in Windows Command Line Interface (CLI) tools, and works the same way as in BIND. The record can be of any type supported by the DNS.
This record is a self-reference, identical to the name of the zone and show up as same as parent folder in Microsoft DNS, or is referred to by an symbol in the BIND zone file. The pinpoint zone usually contains a single record besides the required Start of Authority (SOA) and Name Server records. This allows other DNS queries for this domain to be forwarded to the authoritative sever. This entry can be defined as authoritative on a Name Server, which is not authoritative for the parent domain. The pinpoint DNS entry is a zone created for a single host only. If your network is live, ensure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment. Note: The internal NS is used by internal users, as well as Video Communication System (VCS) / Cisco Expressway-C. Instructions for other types of DNS servers are not provided, but the concept can be used with any other DNS server if the server supports this configuration.
You only need to use the steps appropriate for your particular DNS server. Note: The information in this document can be used either with Microsoft DNS server, or BIND.
PINPOINT PRO OPTICS SOFTWARE
The information in this document is based on these software and hardware versions: A domain which is correctly configured on the public authoritative NS.Prerequisites RequirementsĬisco recommends that you have knowledge of these topics:
PINPOINT PRO OPTICS HOW TO
This document describes how to create pinpoint entries for service records (SRV) on the internal Name Server (NS) in order to work around the lack of split Domain Name System (DNS) setups.Ĭontributed by Zoltan Kelemen, Edited by Joshua Alero and Lidiya Bogdanova, Cisco TAC Engineers.
0 kommentar(er)
