I had a post scheduled talking about eDiscovery. But I got an email from Larry, our senior Lync team member, describing a Lync troubleshooting project he’d just finished for a client.
Well, we just have to document that one for our readers, don’t we?
The Scenario: Everything’s Installed, But is Edge Configured Properly?
Larry was on-site with a client who had some Lync Server 2013 components already installed. However their Edge Server was not communicating with the Front End. What was the problem?
He found no issues on the Front End Server itself. (FYI: Lync Server 2013 Enterprise Edition, Enterprise Voice and Monitoring roles installed.)
So he looked at the Edge Server. It must have a configuration issue, but what kind? He logged directly into the Edge Server and looked through its properties. The Lync Server software was up & running, DNS names were in place…
Wait a second. The Edge Server had a local name only (“companydomain”). What about its suffix?
The DNS Suffix: Necessary for Lync Server Topology
A DNS suffix is required for Edge Servers to communicate with the rest of Lync Server. Topology Builder requires a FQDN (Fully Qualified Domain Name), but by default Edge Servers use short machine names.
The client’s Edge did not have a DNS suffix. This must be why the topology couldn’t communicate with it. We had to add the suffix.
Here are the steps to adding a DNS suffix on an Edge Server:
- On the Edge Server, click Start, right-click Computer, and select Properties.
- Under “Computer Name, Domain, and Workgroup” settings, click Change Settings.
- On the Computer Name tab, click Change.
- You should see the “Computer Name/Domain Changes” screen. Click the More… button.
- The “DNS Suffix and NetBIOS Computer Name” window will pop up. In the Primary DNS suffix of this computer field, type the name of your internal domain (for example, lync.companydomain.com).
- Click OK to close the windows.
- Restart the computer.
(Apologies for the blurring. I used a testing server to create the screenshot, so there’s little risk of hacking. But, better safe than sorry!)
*Important Note: Make sure you restart the server before going any further! Larry did not immediately restart after implementing the DNS suffix (the client asked a question). It took him a moment to realize that THAT’S why he still had communication issues.
Add DNS Records for Edge Lookups
Once the DNS suffix had been added & Edge Server restarted, Larry was able to add the Edge to the existing Lync topology. Time for configuring some DNS records.
DNS records are required for external DNS lookups, perimeter networks and internal client lookups. Some of this was already in place, but Larry had to reconfigure so Edge was fully supported in the Lync architecture.
Here are details on DNS for Edge Servers in Lync Server 2013: Configure DNS for Edge Support in Lync Server 2013 – TechNet
The steps to creating a DNS SRV record:
- On the DNS server, click Start, & open Control Panel.
- Click Administrative Tools, and then click DNS.
- In the console tree for your SIP domain, expand the “Forward Lookup Zones”. Right-click the domain your Lync Server 2013 uses.
- Click Other New Records.
- Under “Select a Resource Record Type”, type Service Location (SRV), and then click Create Record.
- Provide the necessary information to populate the DNS SRV record.
Then, to create a DNS A record:
- Follow Steps 1-3 above to reach the Forward Lookup Zones on your SIP domain.
- Click New Host (A).
- Provide the necessary information for the new DNS record.
Lo and behold, communication worked between Edge and Front End! The client was happy.
DNS Suffix: A Small Addition, but Critical to Edge Communications
If you have trouble with your Edge Servers not cooperating with the Front End, make sure they have FQDNs in place. Otherwise DNS won’t understand proper lookups, and your topology won’t function.
Have you encountered a DNS error with your Edge Server? If so, please comment or email your story in. Did you solve it? Was it a DNS suffix issue, or something else? I’d love to hear about it.
Speaking of hearing about it, I’m a little behind on responding to reader support questions. Not ignoring anyone, I promise. Just wanted to reassure everyone.
Join us here again next week for that discussion on eDiscovery.