#867 The async resolver only tries the first nameserver in /etc/resolv.conf
Closed: Fixed None Opened 12 years ago by sgallagh.

We're not properly failing over to secondary DNS servers if the first server in the list is broken.

Steps to reproduce:

  1. Set up a valid /etc/resolv.conf with a working primary DNS server
  2. Add {{{nameserver 127.0.0.2}}} to the above the working DNS entries (simulates having an unreachable DNS server in the list)
  3. Enable debug logs and restart SSSD

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.

Steps to reproduce:

  1. Set up a valid /etc/resolv.conf with a working primary DNS server
  2. Add {{{nameserver 127.0.0.2}}} to the above the working DNS entries
  3. Enable debug logs and restart SSSD

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.

Steps to reproduce:

  1. Set up a valid /etc/resolv.conf with a working primary DNS server
  2. Add {{{nameserver 127.0.0.2}}} to the above the working DNS entries (simulates having an unreachable DNS server in the list)
  3. Enable debug logs and restart SSSD

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

patch: 0 => 1
status: new => assigned

Fixed by
- 4ebd399 (master)
- a5c7d86 (sssd-1-5)

resolution: => fixed
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to jhrozek
- Issue set to the milestone: SSSD 1.5.8

7 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/1909

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