DNS Records

Successful sign-in to an Edge Server is heavily dependent on correctly configuring the DNS.

• The NSLookup tool can be used to verify that the necessary DNS records are in place as described in Chapter 11, “Dependent Services and SQL.”

Tip

When troubleshooting any Edge Server issue, it is important to check that all necessary DNS records exist and are resolving to the correct IP addresses.

The following sample NSLookup sequence within a command prompt checks the host record of the pool:

nslookup
set type=a
lyncedgepool1.companyabc.com

A successful query returns a name and an IP address. Verify that the IP returned matches the IP addresses assigned to the Edge Servers or load balancer and that no extra, or surprise, IP addresses are returned.

To verify the SRV record required for automatic client sign-in externally, the syntax is slightly different. The following is another sample NSLookup sequence:

nslookup
set type=srv
_sip._tls.companyabc.com

A successful query returns a priority, weight, port, and server hostname. Verify that the server name matches the Edge pool Access Edge FQDN and that the correct port is returned.

Use the same steps to verify that the following services resolve correctly in public DNS:

• Access Edge FQDN

• Web Conferencing Edge FQDN

• A/V Edge FQDN

For internal DNS, verify that clients can resolve the following:

• Internal Edge pool FQDN

Tip

Ensure that the Edge Server can resolve internal DNS names of all Lync Servers. It must be able to properly resolve these DNS entries to communicate with internal servers and users.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset