#388 Async resolver cannot handle extremely long responses
Closed: Fixed None Opened 14 years ago by sgallagh.

When requesting a DNS lookup on a hostname that matches to 60 IP addresses, we receive a UDP response with the TRUNCATED flag set.

When this happens, c-ares (by default) switches to using TCP to perform the lookup. Our c-ares integration in the SSSD cannot handle this properly right now.

I am proposing a short-term solution to set the ARES_FLAG_IGNTC flag for ares_init_options(). This tells c-ares to just use the truncated list it received from UDP, rather than switching to TCP.

This bug is meant to track the longer-term solution of properly handling the TCP lookups.


Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.1

Steps to reproduce this are the same as Ticket #384, except that after fixing the segfault, we were instead getting timeouts.

fixedin: => 1.0.3
resolution: => fixed
status: new => closed

Fields changed

tests: 1 => 0
testsupdated: 0 => 1

Fields changed

rhbz: => 0

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

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

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