Skype for Business 2019 on Premise DNS issues.

%3CLINGO-SUB%20id%3D%22lingo-sub-711098%22%20slang%3D%22en-US%22%3ESkype%20for%20Business%202019%20on%20Premise%20DNS%20issues.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-711098%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20looking%20to%20gain%20some%20assistance%20in%20resolving%20the%20issue%20we%20are%20having%20with%20logging%20into%20Skype%20for%20Business%202019%20on%20premise%20clients.%20When%20trying%20to%20use%20the%20autodiscover%20feature%2C%20we%20receive%20an%20error%20stating%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%22Skype%20for%20Business%20couldn't%20find%20a%20Skype%20for%20Business%20Server%20for%20(domain.com).%20There%20might%20be%20an%20issue%20with%20the%20Domain%20Name%20System%20(DNS)%20configuration%20for%20your%20domain.%20See%20KB2566790%20for%20details%20and%20contact%20your%20system%20admin.%22%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIf%20we%20go%20in%20and%20manually%20set%20the%20internal%2Fexternal%20server%20name%20to%20the%20name%20of%20our%20pool%2C%20we%20are%20able%20to%20sign%20in%20without%20any%20issues.%20I%20have%20checked%20for%20the%20Microsoft%20KB%20listed%20above%2C%20but%20it%20appears%20that%20the%20page%20is%20dead%20and%20can%20not%20find%20any%20assistance%20that%20helps%20us%20with%20our%20issue.%20We%20have%20DNS%20records%20set%20for%20LyncDiscover%20and%20LyncDiscoverInternal%20under%20the%20proper%20domain%20pointing%20at%20the%20name%20of%20our%20pool%2C%20however%20we%20still%20have%20issues%20with%20the%20autodiscover.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20help%20would%20be%20appreciated!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-727462%22%20slang%3D%22en-US%22%3ERe%3A%20Skype%20for%20Business%202019%20on%20Premise%20DNS%20issues.%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-727462%22%20slang%3D%22en-US%22%3E%3CP%3EHello%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F339180%22%20target%3D%22_blank%22%3E%40andyb12321%3C%2FA%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYou%20can%20the%20Skype%20for%20Business%20Diagram%3A%26nbsp%3B%3CA%20href%3D%22https%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fp%2F%3FLinkId%3D550989%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3Ehttps%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fp%2F%3FLinkId%3D550989%3C%2FA%3E%20here%20you%20can%20find%20all%20the%20requirments%20for%20the%20SFB%20Deployment.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHave%20you%20configured%20a%20reverse%20proxy%20for%20your%20webservices%20like%20lyncdiscover.%3CCONTONSO.COM%3E%20and%20configured%20the%20externel%20DNS%20record%20pointing%20to%20your%20SFB%20deployment%3F%3C%2FCONTONSO.COM%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EGreetings%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EErdem%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Occasional Contributor

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!

1 Reply
Highlighted

Hello @andyb12321 

 

You can the Skype for Business Diagram: https://go.microsoft.com/fwlink/p/?LinkId=550989 here you can find all the requirments for the SFB Deployment. 

 

Have you configured a reverse proxy for your webservices like lyncdiscover.<contonso.com> and configured the externel DNS record pointing to your SFB deployment?

 

Greetings,

 

Erdem