Setting up the DNS SRV record
Applies to: Lync 2010 | Lync 2013 | Lync Server 2010 | Lync Server 2013
You can configure the Lync Dialog Listener (LDL) to query DNS for the location of the host or pool of the Lync SDN Manager (LSM) Service, if the DNS SRV record was created properly. This article explains how to create the SRV records. You must have domain administrator privileges to do this.
Note
When DNS "Service Location (SRV)" records are used by LDL, any configured value for the parameter submitURI is ignored. Instead, the URI specified in the SRV record is used.
To set up the DNS SRV record
Log on to the DNS server and open the DNS Manager
Open DNS and choose the zone to create the SRV record for (Current domain, forward lookup zone).
From the Context menu, select Other New Records..., navigate to Service Location (SRV), and choose Create Record.
Fill in the form (shown in the following figure), specifying _sdninternal to the Service: input box.
- Enter an FQDN of the host computer (for example, SdnPool.LneProd.contoso.com) to the Host offering the LSM service.
- Select _http (_https) in the Protocol: field.
- Select 9333 (9332) in the Port number: input box.
Note
If both the HTTP and HTTPS protocols are specified, the HTTP SRV record is ignored until the HTTPS record is deleted.
After the SRV discovery is configured, the following behavior will occur:
If the HTTPS protocol is used, the LDL looks for the _sdninternal service address. Otherwise, the LDL attempts to retrieve the address of an SDN Manager service using the HTTP protocol. It then creates a service URL with the service name ("LDL") appended at the end. An example of the resulting URL is https://SdnPool.LneProd.contoso.com:9332/LDL.
You can enable LDL to check SRV record to discover the LSM locations by selecting the appropriate settings in the LDL Installation Wizard or by editing the LyncDialogListener.exe.config file and setting the following entry.
<add key="checkdns" value="True"/>
See also
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for