brookesm
asked on
Lync Server 2010 DNS problem
Hi All,
I have installed Microsoft Lync Server 2010 - standard edition. I have managed to get everything working except getting the clients to connect automatically. I have adding the SRV record correctly and the Host A record, I have checked that I can ping the FQDN of the standard edition server and have also done an nslookup and all bring back the correct results. I think I know what the issue is but don't know how to correct it so here it is...
My FQDN of my server is servername.zone.mydomain.a
//////////////////////////
Communicator was unable to locate the login server. No DNS SRV records exist for domain mydomain.ac.uk, so Communicator was unable to login.
Resolution:
Please double-check the server name to make sure that it is typed correctly. If it is correct, the network administrator will either need to use manual configuration to specify the login server's fully-qualified domain name (FQDN), or add DNS SRV records for the mydomain.ac.uk domain in order to allow automatic client configuration. The DNS SRV records _sipinternaltls._tcp.mydom
//////////////////////////
As you can see the two domain names do not match...for some reason the client is trying to connect to mydomain.ac.uk instead of zone.mydomain.ac.uk. I assume I must have configured something incorrectly during installation, however I have checked and re-created the topology with the correct FQDN of the server and the FQDN of the SIP domain. Does anyone have any suggestions I can try to resolve this?
Thanks
Natalie
I have installed Microsoft Lync Server 2010 - standard edition. I have managed to get everything working except getting the clients to connect automatically. I have adding the SRV record correctly and the Host A record, I have checked that I can ping the FQDN of the standard edition server and have also done an nslookup and all bring back the correct results. I think I know what the issue is but don't know how to correct it so here it is...
My FQDN of my server is servername.zone.mydomain.a
//////////////////////////
Communicator was unable to locate the login server. No DNS SRV records exist for domain mydomain.ac.uk, so Communicator was unable to login.
Resolution:
Please double-check the server name to make sure that it is typed correctly. If it is correct, the network administrator will either need to use manual configuration to specify the login server's fully-qualified domain name (FQDN), or add DNS SRV records for the mydomain.ac.uk domain in order to allow automatic client configuration. The DNS SRV records _sipinternaltls._tcp.mydom
//////////////////////////
As you can see the two domain names do not match...for some reason the client is trying to connect to mydomain.ac.uk instead of zone.mydomain.ac.uk. I assume I must have configured something incorrectly during installation, however I have checked and re-created the topology with the correct FQDN of the server and the FQDN of the SIP domain. Does anyone have any suggestions I can try to resolve this?
Thanks
Natalie
Try adding sip.yourdomain.com pointing to your FE server.
ASKER
What kind of DNS record? Host A?
Try it out as a Host A.
ASKER
No that didn't work. Any other suggestions?
Did you log out/in of Windows afterwards? Try adding it as a cname then, but I'm not sure if it'll work. You're certain you've added the SRV records correctly, as described in your question?
Have a look at the requirements here:
http://technet.microsoft.com/en-us/library/gg398082.aspx
http://technet.microsoft.com/en-us/library/gg398082.aspx
ASKER
Hi,
Yes I have added the SRV and Host A records for my domain, however the error returned is not for the FQDN of hsfc.mydomain.ac.uk it is for mydomain.ac.uk so for some reason it is not using the FQDN and I don't know why!
Thanks
Yes I have added the SRV and Host A records for my domain, however the error returned is not for the FQDN of hsfc.mydomain.ac.uk it is for mydomain.ac.uk so for some reason it is not using the FQDN and I don't know why!
Thanks
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.