SSSD should use all DNS search domains in resolv.conf

[sssd-bot]

Cloned from Pagure issue: https://pagure.io/SSSD/sssd/issue/987

• Created at 2011-08-31 14:53:52 by sgallagh
• Closed at 2020-03-24 14:22:13 as wontfix
• Assigned to nobody
• Associated bugzillas
  • https://bugzilla.redhat.com/show_bug.cgi?id=771964

---

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.

Comments

---

Comment from sgallagh at 2011-09-01 15:43:17

Fields changed

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

---

Comment from dpal at 2012-01-05 15:29:39

Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=771964

rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=771964 771964]

---

Comment from dpal at 2012-01-05 15:30:19

Fields changed

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

---

Comment from dpal at 2012-01-16 17:01:22

"Nice to have" for 1.9.

milestone: SSSD 1.9.0 NEEDS_TRIAGE => SSSD 1.9.0

---

Comment from dpal at 2012-02-09 15:44:23

Fields changed

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

---

Comment from dpal at 2012-08-16 13:36:32

Fields changed

proposed_priority: => Nice to have

---

Comment from dpal at 2012-09-04 23:20:30

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

milestone: SSSD 1.11 beta => SSSD 1.10 beta

---

Comment from dpal at 2012-12-20 23:33:42

Fields changed

selected: => Not need

---

Comment from dpal at 2013-01-02 15:32:08

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

milestone: SSSD 1.10 beta => SSSD 1.11 beta

---

Comment from dpal at 2014-09-26 18:49:56

Fields changed

mark: => 0

---

Comment from jhrozek at 2015-02-10 17:00:12

Fields changed

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

---

Comment from jhrozek at 2015-02-12 20:35:51

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

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

---

Comment from sgallagh at 2017-02-24 14:48:56

Metadata Update from @sgallagh:

• Issue set to the milestone: SSSD Patches welcome

---

Comment from pbrezina at 2020-03-24 14:22:12

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.

---

Comment from pbrezina at 2020-03-24 14:22:13

Metadata Update from @pbrezina:

• Issue close_status updated to: wontfix
• Issue status updated to: Closed (was: Open)