locked
Skype for Business Server 2019 On-Premise DNS issue RRS feed

  • Question

  • We are looking to gain some assistance in resolving the issue we are having with logging into Skype for Business 2019 on premise clients. When trying to use the autodiscover feature, we receive an error stating:

    "Skype for Business couldn't find a Skype for Business Server for (domain.com). There might be an issue with the Domain Name System (DNS) configuration for your domain. See KB2566790 for details and contact your system admin."

    If we go in and manually set the internal/external server name to the name of our pool, we are able to sign in without any issues. I have checked for the Microsoft KB listed above, but it appears that the page is dead and can not find any assistance that helps us with our issue. We have DNS records set for LyncDiscover and LyncDiscoverInternal under the proper domain pointing at the name of our pool, however we still have issues with the autodiscover.

    Any help would be appreciated!

    Thursday, June 20, 2019 3:22 PM

All replies

  • Skype for Business has a lot of DNS entry requirements to work with. There are the lyncdiscover records, but you also need sip DNS records, sipinternaltls SRV records, etc. https://docs.microsoft.com/en-us/skypeforbusiness/plan-your-deployment/network-requirements/dns covers the whole list of DNS records for SfB Server.
    • Proposed as answer by Shaw_Lu Monday, June 24, 2019 6:11 AM
    Thursday, June 20, 2019 3:30 PM
  • Hi Andrew,

    Are the client machines domain-joined or non-domain-joined?

    Could you resolve the DNS records on the affected machines?

    Please refer to DNS configuration as below:

    In addition, use “Remote Connectivity Analyzer” to check the server side configuration.

    https://testconnectivity.microsoft.com/


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    • Proposed as answer by Shaw_Lu Monday, June 24, 2019 6:11 AM
    Friday, June 21, 2019 1:29 AM
  • Hi,

    Just checking that the lyncdiscoverinternal A record is in the SIP domain DNS zone and not your internal zone if for example you have domain.local and then domain.com as your SIP domain?

    Lyncdiscoverinternal is the 1st record it checks so just ensure the above is setup correctly in the correct zone.

    Regards

    • Proposed as answer by Shaw_Lu Monday, June 24, 2019 6:11 AM
    Friday, June 21, 2019 8:50 PM
  • Hi,

    Do you have any further issue on this topic?

    Meanwhile, if there is no issue, please remember to mark helpful reply as answer to close the thread. Your action would be helpful to other users who encounter the same issue and read this thread.

    Thanks for your understanding.


    Best Regards,
    Shaw Lu


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnsf@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Thursday, June 27, 2019 9:54 AM