Domain Name System (DNS) requirements for Lync Server 2013
Topic Last Modified: 2012-06-18
To deploy Lync Server, you must create Domain Name System (DNS) records that enable the discovery of clients and servers, and, optionally, support for automatic client sign-in if your organization wants to support it.
Lync Server uses DNS in the following ways:
To discover internal servers or pools for server-to-server communications.
To allow clients to discover the Front End pool or Standard Edition server used for various SIP transactions.
To allow unified communications (UC) devices that are not logged on to discover the Front End pool or Standard Edition server running Device Update Web Service, obtain updates, and send logs.
To allow external servers and clients to connect to Edge Servers or the HTTP reverse proxy for instant messaging (IM) or conferencing.
To allow external UC devices to connect to Device Update Web service through Edge Servers or the HTTP reverse proxy and obtain updates.
To allow mobile clients to automatically discover Web Services resources without requiring users to manually enter URLs in device settings.
In This Section
We'd love to hear your thoughts. Choose the type you'd like to provide:
Our feedback system is built on GitHub Issues. Read more on our blog.