Setting Up DNS for Devices
Topic Last Modified: 2012-06-21
Ensure that the following records are published to a Domain Name System (DNS) service within the corporate network.
| Type | Value | Note |
|---|---|---|
A |
Fully qualified domain names (FQDNs) for the cluster(s) hosting the Registrars |
If using hardware load balancing, specify A records for each cluster that contains a Registrar.If you are using the new DNS load balancing feature in Lync Server, specify the server FQDN and the cluster FQDN, using the same IP address. This must be done for each server in the cluster. A record must be created for each cluster that contains a Registrar.For example:
|
SRV |
_sipinternal._tcp.<SIP domain>_sipinternaltls._tcp.<SIP domain> |
Two SIP FQDNs for internal routing, one for communications over TCP, and one for TCP communications that use TLS. |
A |
ucupdates-r2.<SIP domain> |
The Web Services portion of the Device Update Server URL. The device appends “:443/RequestHandler/ucdevice.upx”. Make sure the HLB translates external requests to use :4443/RequestHandler/ucdevice.upx”, ie the external port is 4443. |
If setting up external access, the following records must also be hosted in a public DNS server:
| Type | Value | Note |
|---|---|---|
SRV |
Edge Server:_sipexternal._tls.<SIP domain>, and _sipexternaltls.<SIP domain> |
Allows external devices to connect by using SIP over TLS to the Registrar internally. |
A |
Reverse proxy FQDN:<server name>.<SIP domain> |
Allows external devices to connect by using TLS over HTTP to the Device Update Web service. LLDP-enabled switches within the enterprise will be used to provide VLAN IDs, or the decision is made not to use VLAN for Lync Server communications. |