Learn more about these different git repos.
Other Git URLs
Although ipa_dyndns_update is really an awesome feature, it occurred to me that it always unconditionally attempts an update even if the record is already correct.
It would be advisable to verify an update is actually needed before performing it, because modification of the DNS tables is not free of cost and should be avoided when not necessary.
In the ipa case it increases the amount of ldap data that needs to be replicated around, and may cause slave DNS servers to notice a new serial and perform zone transfers even when not really needed.
Fields changed
milestone: NEEDS_TRIAGE => SSSD 1.6.0
owner: somebody => jhrozek
cc: => jhrozek
component: SSSD => IPA Provider patch: => 0
status: new => assigned
master: 7e2de11
resolution: => fixed status: assigned => closed
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=785883
rhbz: => [https://bugzilla.redhat.com/show_bug.cgi?id=785883 785883]
Metadata Update from @simo: - Issue assigned to jhrozek - Issue set to the milestone: SSSD 1.6.0
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/1844
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.