Bug 743503 - [RFE] sssd should support DNS sites
Summary: [RFE] sssd should support DNS sites
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: sssd
Version: 7.0
Hardware: All
OS: Linux
high
low
Target Milestone: rc
: 7.0
Assignee: Jakub Hrozek
QA Contact: Kaushik Banerjee
URL:
Whiteboard:
Depends On:
Blocks: 747612 1044729
TreeView+ depends on / blocked
 
Reported: 2011-10-05 07:12 UTC by Ondrej Valousek
Modified: 2020-05-02 16:27 UTC (History)
7 users (show)

Fixed In Version: sssd-1.10.0-10.el7.beta2
Doc Type: Enhancement
Doc Text:
Feature: The SSSD is able to locate the nearest Active Directory Domain Controller using the Active Directory "sites" feature, similar to how Windows clients work. Reason: In large environments, especially geographically distributed, it is common to have several "sites" defined in DNS and the client should be automatically directed to the nearest site to avoid connecting to a distant server. Result (if any): The SSSD transparently connects to the site as defined on the Active Directory server side and is able to fail over to the other sites in case the primary one is unreachable.
Clone Of:
: 1044729 (view as bug list)
Environment:
Last Closed: 2014-06-13 13:27:15 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Github SSSD sssd issues 2074 0 None None None 2020-05-02 16:27:14 UTC

Description Ondrej Valousek 2011-10-05 07:12:18 UTC 
SSSD should support DNS "sites" concept known from Active Directory. Example:
Example AD domain CONTOSO.COM used on 3 sites - Prague,Cork, Dublin.
I have machine in Prague and I want it to join CONTOSO.COM. Now if I used:
 
dns_discovery_domain = contoso.com
 
sssd would try to connect to any DC in the domain - even the one in Dublin, completely ignoring sites.
I have to use:
 
dns_discovery_domain = Prague._sites.contoso.com
 
To force it to use Prague DCs only.
My understanding is, that the "DC locator" tries to communicate with DC's first to determine local site and remote DC's are only used if no valid/working DC can be found in the local site (Prague in this case).

This is AD specific functionality, but this concept would find its use also in large IPA domains where multiple IPA servers for the same domain exist in demographically different sites.

I believe some of the necessary code can be "stolen" from the Samba winbind component which implements this functionality
Comment 3 Stephen Gallagher 2011-10-05 11:58:49 UTC 
Upstream ticket:
https://fedorahosted.org/sssd/ticket/1032
Comment 5 Jakub Hrozek 2013-05-02 15:04:28 UTC 
Pushed upstream.
Comment 6 Jakub Hrozek 2013-10-04 13:25:11 UTC 
Temporarily moving bugs to MODIFIED to work around errata tool bug
Comment 9 Ludek Smid 2014-06-13 13:27:15 UTC 
This request was resolved in Red Hat Enterprise Linux 7.0.

Contact your manager or support representative in case you have further questions about the request.
Note You need to log in before you can comment on or make changes to this bug.