Udostępnij za pośrednictwem


Configure DNS for load balancing in Lync Server 2013

 

Topic Last Modified: 2012-10-01

To successfully complete this procedure, you should be logged on to the server or domain minimally as a member of the Domain Admins group or a member of the DnsAdmins group.

Domain Name System (DNS) Load Balancing balances the network traffic that is unique to Lync Server 2013, such as SIP traffic and media traffic. DNS load balancing is supported for Front End pools, Edge pools, Director pools, and stand-alone Mediation pools. A pool that is configured to use DNS load balancing must have two fully qualified domain names (FQDNs) defined: the regular pool FQDN that is used by DNS load balancing (for example, pool1.contoso.com) and that resolves to the physical IPs of the servers in the pool, and another FQDN for the pool’s Web Services (for example, web1.contoso.net), which resolves to the virtual IP address of the pool. For details about DNS Load Balancing, see DNS load balancing in Lync Server 2013 in the Planning documentation.

Note

Hardware load balancing is still required for client to server HTTPS traffic.

Before you can use DNS load balancing, you must do the following:

  1. Override the internal Web Services pool FQDN.

    Warning

    If decide to override the Internal web services with a self-defined FQDN, each FQDN must be unique from any other Front End pool, Director or a Director pool.

  2. Create DNS A host records to resolve the pool FQDN to the IP addresses of all the servers in the pool.

  3. Enable IP Address randomization or, for Windows Server DNS, enable round robin.

    Note

    Round robin should be enabled by default.

To override internal Web services FQDN

  1. Start Topology Builder: Click Start, click All Programs, click Microsoft Lync Server 2013, and then click Lync Server Topology Builder.

  2. From the console tree, expand the Enterprise Edition Front End pools node.

  3. Right-click the pool, click Edit Properties, and then click Web Services.

  4. Below Internal web services, select the Override FQDN check box.

  5. Type the pool FQDN that resolves to the physical IP addresses of the servers in the pool.

  6. Below External web services, type the external pool FQDN that resolves to the virtual IP addresses of the pool, and then click OK.

  7. From the console tree, click Lync Server 2013, and then in the Actions pane, click Publish Topology.

To create DNS Host (A) Records for all internal pool servers

  1. Click Start, click All Programs, click Administrative Tools, and then click DNS.

  2. In DNS Manager, click the DNS Server that manages your records to expand it.

  3. Click Forward Lookup Zones to expand it.

  4. Right-click the DNS domain that you need to add records to, and then click New Host (A or AAAA).

  5. In the Name box, type the name of the host record (the domain name will be automatically appended).

  6. In the IP Address box, type the IP address of the individual Front End Server and then select Create associated pointer (PTR) record or Allow any authenticated user to update DNS records with the same owner name, if applicable.

  7. Continue creating records for all member Front End Servers that will participate in DNS Load Balancing.

    For example, if you had a pool named pool1.contoso.com and three Front End Servers, you would create the following DNS entries:

    FQDN Type Data

    Pool1.contoso.com

    Host (A)

    192.168.1.1

    Pool1.contoso.com

    Host (A)

    192.168.1.2

    Pool1.contoso.com

    Host (A)

    192.168.1.3

    For details about creating DNS Host (A) records, see Configure DNS Host records for Lync Server 2013.

To enable round robin for Windows Server

  1. Click Start, click All Programs, click Administrative Tools, and then click DNS.

  2. Expand DNS, right-click the DNS server you want to configure, and then click Properties.

  3. Click the Advanced tab, select Enable round robin and Enable netmask ordering, and then click OK.

    DNS Round Robin dialog box

Note

This feature should be enabled by default.