#1884 [RFE] Read and use the TTL value when resolving a SRV query
Closed: Fixed None Opened 7 years ago by jhrozek.

The retry time to resolve a SRV query is currently hardcoded. That limitation comes from the past where the underlying resolver library had no way of returning the TTL to the user. We should change the hardcoded interval to honor the TTL (we already honor it for A/AAAA requests).


Fields changed

type: defect => enhancement

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12 beta
rhbz: => todo

This ticket and #2511 were requested by downstream support case. Bumping up to NEEDS_TRIAGE.

changelog: =>
mark: => 0
milestone: SSSD 1.14 beta => NEEDS_TRIAGE

Fields changed

owner: somebody => jhrozek
status: new => assigned

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.12.4

Fields changed

priority: major => critical

Fields changed

patch: 0 => 1

Moving tickets that didn't make the 1.12.4 release to 1.12.5

milestone: SSSD 1.12.4 => SSSD 1.12.5

resolution: => fixed
status: assigned => closed

Also related commits are:
- 9797aa5
- 842fe49
- bf54fbe
- 2be2220

sensitive: => 0

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

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

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