I am struggling with getting a Lync client to talk to a new server. I've turned on logging at the client...it shows that it has to do with the SRV record, which appears to bite a lot of people.
Here's my scenario:
Lync server is intended solely for internal use and internal video conferencing. Perhaps this will change in the future but for now that's the focus.
My real Active Directory domain is named in this format: local.abc.net
I set my Lync SIP domain to : abc.net
I have DNS A records for dialin.abc.net, meet.abc.net and admin URL lync.abc.net
I created an SRV record for meet.abc.net
Here's the sticky part:
Our email domain is: xyz.com
I'm sure this is where the problem lies...just not sure how to go about dealing with it on the DNS side. Is there some kind of DNS trick that will resolve this problem? We do not have a zone for xyz.com in our DNS. Can this be added such that it would have NO bearing on any other network actions? Is this the way to go?
Or...should I reinstall Lync using a SIP domain of xyz.com? Would that not just introduce DNS problems from the "other" side?
I know I can pursue the GPO setting angle...but I want to fully know that GPO would be the *only* way to do it before I go that route.