DNS Requirements for Standard Edition Servers
Topic Last Modified: 2010-12-12
This section describes the Domain Name System (DNS) records that are required for deployment of Standard Edition servers.
DNS Records for Standard Edition Servers
The following table specifies DNS requirements for Microsoft Lync Server 2010 Standard Edition server deployment.
DNS Requirements for a Standard Edition Server
| Deployment scenario | DNS requirement |
|---|---|
Standard Edition server |
An internal A record that resolves the fully qualified domain name (FQDN) of the server to its IP address. |
Automatic client sign-in |
For each supported SIP domain, an SRV record for _sipinternaltls._tcp.<domain> over port 5061 that maps to the FQDN of the Standard Edition server that authenticates and redirects client requests for sign-in. For details, see DNS Requirements for Automatic Client Sign-In. |
Device Update Web service discovery by unified communications (UC) devices |
An internal A record with the name ucupdates-r2.<SIP domain> that resolves to the IP address of the Standard Edition server hosting Device Update Web service. In the situation where a UC device is turned on, but a user has never logged into the device, the A record allows the device to discover the server hosting Device Update Web service and obtain updates. Otherwise, devices obtain the server information though in-band provisioning the first time a user logs in. For details, see Updating Devices in the Planning documentation. Important If you have an existing deployment of Device Update Web service in Office Communications Server 2007, you have already created an internal A record with the name ucupdates.<SIP domain>. For Office Communications Server 2007 R2, you must create an additional DNS A record with the name ucupdates-r2.<SIP domain>. |
A reverse proxy to support HTTP traffic |
An external A record that resolves the external web farm FQDN to the external IP address of the reverse proxy. Clients and UC devices use this record to connect to the reverse proxy. For details, see Determining DNS Requirements in the Planning documentation. |