Create and Configure DNS Records
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.
During migration, the existence of the new Office Communications Server 2007 R2 pool will require that users be authenticated on the existing Office Communications Server 2007 pool and be redirected from there.
The DNS SRV record can point only to a single pool, and in a mixed environment the supported configuration is to use Office Communications Server 2007, Director, with both Office Communications Server 2007 and Office Communications Server 2007 R2 pools. This means that during migration, you should configure DNS records to point to the Office Communications Server 2007 Director. After the Office Communications Server 2007 pool is decommissioned and you have an Office Communications Server 2007 R2 Director in place, you can update the SRV record to the new Office Communications Server 2007 R2 Director. You will need to make the appropriate changes to the _sipinternaltls._tcp
DNS record. For more information, see Create and Verify DNS Records for Your Server or Pool in the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation.
You must create and configure internal and external DNS records to support the new system after you have upgraded your Directors and other next-hop servers. To create these DNS records:
For each Standard Edition server and Enterprise pool, create the records as explained in Create and Verify DNS Records for Your Server or Pool in the Deploying Office Communications Server 2007 R2 Enterprise Edition documentation.
For each edge server or edge server array, create the records as explained in DNS Requirements for External User Access in the Planning and Architecture documentation.
Note
Do not make any changes to existing DNS records. After you have deprecated the existing servers, you will remove these records.
If your Office Communications Server 2007 R2 deployment will include a Director and Edge Server and you intend to allow access to external users who are homed on the new pool, you will need to prepare a complete set of DNS records to support Office Communications Server 2007 R2, Edge Server. Because Office Communications Server 2007 is servicing the SIP domain, the Office Communications Server 2007 R2 pool, Director, and Edge Server will not be able to participate in federation or public IM connectivity unless you create a new organization and a new SIP domain just for the new pool. For details, see DNS Requirements for External User Access in the Planning and Architecture documentation.