#1992 AD dyndns update crashed after attempting to update a standalone DNS server
Closed: Fixed None Opened 9 years ago by jhrozek.

In Red Hat bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=975001 a crash of dyndns update was described. The crash occured when the SSSD attempted to perform a DNS update from an AD provider while the DNS server was not the AD server, but rather a standalone one (dnsmasq on a host, the AD provider was running in a VM pointing to the host)

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10.1
rhbz: => todo

Fields changed

rhbz: todo => 976573

Fields changed

cc: => dwmw2@infradead.org

Fields changed

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

My guess is that dyndns update timed out, thus the req does not exist anymore when nsupdate finally finishes and nsupdate_child_handler() is fired.

Fields changed

patch: 0 => 1

resolution: => fixed
status: assigned => closed

Fields changed

changelog: => N/A, just a bugfix

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

5 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/3034

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.