Learn more about these different git repos.
Other Git URLs
We're not properly failing over to secondary DNS servers if the first server in the list is broken.
Steps to reproduce:
The debug log will contain
(Wed May 11 16:08:52 2011) [sssd[be[example.com]]] [fo_resolve_service_done] (1): Failed to resolve server 'ldap.example.com': Could not contact DNS servers
and SSSD will operate permanently in offline mode because it can never resolve the SRV records.
It's unclear right now whether the bug is in SSSD's async resolver or internal to the c-ares library.
Fields changed
description: We're not properly failing over to secondary DNS servers if the first server in the list is broken.
The debug log will contain {{{ (Wed May 11 16:08:52 2011) [sssd[be[example.com]]] [fo_resolve_service_done] (1): Failed to resolve server 'ldap.example.com': Could not contact DNS servers }}} and SSSD will operate permanently in offline mode because it can never resolve the SRV records.
It's unclear right now whether the bug is in SSSD's async resolver or internal to the c-ares library. => We're not properly failing over to secondary DNS servers if the first server in the list is broken.
patch: 0 => 1 status: new => assigned
Fixed by - 4ebd399 (master) - a5c7d86 (sssd-1-5)
resolution: => fixed status: assigned => closed
rhbz: => 0
Metadata Update from @sgallagh: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.5.8
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/1909
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Login to comment on this ticket.