DNS Requirements for Enterprise Pools

Microsoft Office Communications Server 2007 and Microsoft Office Communications Server 2007 R2 will reach end of support on January 9, 2018. To stay supported, you will need to upgrade. For more information, see Resources to help you upgrade your Office 2007 servers and clients.

 

Topic Last Modified: 2015-03-09

This section describes the DNS records that are required for deployment of Enterprise pools.

DNS Records for Enterprise Pools

The following table specifies DNS requirements for Office Communications Server 2007 R2 Enterprise pool deployment.

Table 1. DNS Requirements for an Enterprise Pool

Deployment scenario	DNS requirement
Enterprise pool with multiple Front End Servers and a required load balancer	An internal A record that resolves the FQDN of your Enterprise pool to the virtual IP address of the load balancer.
Enterprise pool with a single Front End Server and a dedicated Back-End Database but no load balancer	An internal A record that resolves the FQDN of the Enterprise pool to the IP address of the single Enterprise Edition server.
An internal URL for Web conferencing that is different from the default pool FQDN	An internal A record that resolves the host name portion of the URL to the virtual IP of the Web conferencing load balancer (or single Front End Server if appropriate).
Automatic client logon	For each supported SIP domain, an SRV record for _sipinternaltls._tcp.<domain> over port 5061 that maps to the FQDN of the Enterprise pool that authenticates and redirects client requests for sign-in. For details, see DNS Requirements for Automatic Client Sign-In.
Device Update Service discovery by UC devices	An internal A record with the name ucupdates-r2.<SIP domain> that resolves to the IP address of the Enterprise pool hosting Device Update Service. In the situation where an Office Communications Server 2007 R2 UC device is turned on, but a user has never logged into the device, the A record allows the device to discover the Enterprise pool hosting Device Update Service and obtain updates. Otherwise, devices obtain this information though in-band provisioning the first time a user logs in. For details, see Device Update Service. Important If you have an existing deployment of Software Update Server 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 Web conferencing for external users as well as access to Device Update Service by external UC devices	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 DNS Requirements for External User Access.

The following table shows an example of the DNS records required for the internal Web farm FQDN.

Table 2. Example DNS Records for Internal Web Farm FQDN

Internal Web farm FQDN	Pool FQDN	DNS A record(s)
EEpool.contoso.com	EEpool.contoso.com	DNS A record for EEpool.contoso.com that resolves to the virtual IP (VIP) address of the load balancer used by the Enterprise Edition servers in the pool. In this case, the load balancer distributes SIP traffic to the Front End Servers and HTTP(S) traffic to the Web Components Servers.
Meetings.internal.contoso.com	EEpool.contoso.com	DNS A record for the EEpool.contoso.com that resolves to the VIP address of the load balancer used by the Front End Servers. DNS A record for Meetings.internal.contoso.com that resolves to the VIP address of the load balancer used by the Web Components Servers.