#987 SSSD should use all DNS search domains in resolv.conf
Closed: wontfix 3 years ago by pbrezina. Opened 12 years ago by sgallagh.

Currently, SSSD uses the following algorithm to determine which DNS domain to search for auto-discorvery:

  1. If {{{dns_discovery_domain}}} is set in sssd.conf, that is definitive.
  2. Try to use {{{hostname -d}}}
  3. Fall back to using the SSSD domain name in sssd.conf

It would be better if we used the search domains specified in {{{/etc/resolv.conf}}}

So I suggest the algorithm should be:

  1. If {{{dns_discovery_domain}}} is set in sssd.conf, that is definitive.
  2. Iterate through /etc/resolv.conf search domains
  3. Try to use {{{hostname -d}}}
  4. Fall back to using the SSSD domain name in sssd.conf

This way we'll prioritize the new approach, but leave the existing approach as a fallback option.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.8.0
priority: major => minor

Fields changed

blockedby: =>
blocking: =>
milestone: SSSD 1.8.0 => SSSD 1.9.0 NEEDS_TRIAGE

"Nice to have" for 1.9.

milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD 1.9.0

Fields changed

feature_milestone: =>
milestone: SSSD 1.9.0 => SSSD 1.11 beta

Fields changed

proposed_priority: => Nice to have

Moving all the features planned for 1.10 release into 1.10 beta.

milestone: SSSD 1.11 beta => SSSD 1.10 beta

Fields changed

selected: => Not need

Moving tickets that are not a priority for SSSD 1.10 into the next release.

milestone: SSSD 1.10 beta => SSSD 1.11 beta

Fields changed

mark: => 0

Fields changed

changelog: =>
design: =>
design_review: => 0
fedora_test_page: =>
milestone: SSSD 1.13 beta => SSSD 1.13 backlog
priority: minor => trivial
review: => 0

Mass-moving tickets not planned for any immediate release and re-setting priority.

milestone: SSSD 1.13 backlog => SSSD Deferred
priority: trivial => major

Metadata Update from @sgallagh:
- Issue set to the milestone: SSSD Patches welcome

7 years ago

Thank you for taking time to submit this request for SSSD. Unfortunately this issue was not given priority and the team lacks the capacity to work on it at this time.

Given that we are unable to fulfill this request I am closing the issue as wontfix.

If the issue still persist on recent SSSD you can request re-consideration of this decision by reopening this issue. Please provide additional technical details about its importance to you.

Thank you for understanding.

Metadata Update from @pbrezina:
- Issue close_status updated to: wontfix
- Issue status updated to: Closed (was: Open)

3 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/2029

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Login to comment on this ticket.

Metadata