A quick post to let followers of my Remote UC Troubleshooting Tool (RUCT) for Lync and OCS know that the DNS records used by the Lync mobility clients to auto-discover the Lync mobility service have been added.
Specifically you now have the option of querying the locally configured DNS server for the following records:
- Lyncdiscover.<domain.com> (both CNAME or A record)
- Lyncdiscoverinternal.<domain.com> (both CNAME or A record)
From the same screen you can ping the resulting hostname or test the port availability on any of the Lync DNS record matches.
Here is a sample screen shot with the Lync Auto-Discovery Mobility DNS record:
See http://blog.insideocs.com/2011/11/14/the-remote-uc-troubleshooting-tool-ruct/ for more information on this free Windows tool.
More information about the Lync Mobility DNS records can be found here:
- Lync 2010 Mobility – Do I need lyncdiscoverinternal?
- Lync Mobility, lyncdiscoverinternal or lyncdiscover
- Microsoft TechNet – Technical Requirements for Mobility
- Microsoft Lync 2010 for the iPhone and iPad Released
Twitter
LinkedIn
Hi,
I tried to reproduce the problem and couldn’t. I assume the sip domain your are entering is “domain.co.nz”. When I use this sip domain, I don’t get a match for sip.domain.co.nz – even on Google public DNS servers. I do get a match on other Lync DNS records (such as the simple URL’s).
I don’t know why it would be adding the parent domain twice either…Could this be a mis-configuration on the client DNS settings?
If you can send me the contents of the application logging tab, that would help.
Thanks,
Curtis
I downloaded and ran the RUCT tool tonight for a play. It seems that all the IP addresses are resolving incorrectly for me.
e.g. displayed is:
Record: sip.domain.co.nz
Type: A
Hostname: sip.domain.co.nz.co.nz (added the parent domain suffix again)
IP Address: 119.47.114.167 (which is the ip address returned by the .co.nz.co.nz domain squatter..)
why is the tool resolving the host and adding parent domain (.co.nz) automatically? The records are already FQDNs.