You need to use tool AD sites and services to create AD site first
(you should have done that anyway if you have AD controllers behind
a slow VPN link).
On 09/18/2012 03:56 PM, Michael Cronenworth wrote:
Ondrej Valousek wrote:
I had the same problem and instead of had-coding our local AD server
(which is ugly) I used dns_discovery_domain in form of:
<your site name>._sites.<ad realm>
This way you ensure sssd is always using local AD controller to your site.
So if my AD was: test-ad-01.example.com
My conf file would look like:
dns_discovery_domain = test-ad-01._sites.example.com
sssd-users mailing list