RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
Sssd AD (and probably IPA) provider's failing dynamic DNS updates are not retried, another update attempt is only done after refresh interval.

With default refresh interval, a failed update means than new or changed host DNS records wouldn't be created for at least another 24 hours.

Version-Release number of selected component (if applicable):
1.11.2-29.el7.x86_64

How reproducible:
Always.

Note for potential implementation - http://tools.ietf.org/html/rfc1536#section-1 :
[...]
   Both name servers and stub
   resolvers should, therefore, implement some kind of a retransmission
   policy based on round trip time estimates of the name servers. The
   client should back-off exponentially, probably to a maximum timeout
   value.
[...]

Note that nsupdate, by default, seem to do 3 attempts to do the update, with 3 seconds in between. So, sssd shouldn't do it, but indeed some exponential retry scheme might be used instead.

I'm not against three successive attempts with timeout = 3 seconds but then the timeout raise exponentially.

Upstream ticket:
https://fedorahosted.org/sssd/ticket/2206

Makes sense, but not too urgent for 7.3

Since this problem is already tracked in an upstream ticket and this bugzilla is not being planned for any immediate release either in RHEL or upstream, I'm closing this bugzilla with the resolution UPSTREAM.

Please reopen this bugzilla report if you disagree.