SSSD / sssd

#701 Dynamic DNS update not working
Closed: Invalid Opened by sgallagh.

Closed: Invalid
Reopen Issue 
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [ipa_dyndns_update_send] (9): Performing update
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [sdap_id_op_connect_step] (9): reusing cached connection
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [sdap_id_op_destroy] (9): releasing operation connection
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [child_handler_setup] (8): Setting up signal handler up for pid [1926]
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [child_handler_setup] (8): Signal handler set up for pid [1926]
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [write_pipe_handler] (6): All data has been sent!
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [ipa_dyndns_stdin_done] (9): Sending nsupdate data complete
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [child_sig_handler] (7): Waiting for child [1926].
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [child_sig_handler] (1): child [1926] failed with status [1].
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [ipa_dyndns_child_handler] (1): Dynamic DNS child failed with status [256]
(Mon Dec  6 14:20:02 2010) [sssd[be[idm.lab.bos.redhat.com]]] [ipa_dyndns_update_done] (1): Updating DNS entry failed

However, running {{{nsupdate -g}}} from the command line works properly.

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.5.0
priority: major => trivial

Fields changed

status: new => assigned

This looks like it's not actually an SSSD issue. It appears to be a permissions problem on the IPA server. IPA is denying access to write or delete AAAA records, so we're getting an error message back in the SSSD logs.

Interestingly, the IPv4 records are still updated. I'm taking this to the FreeIPA team for additional investigation.

https://fedorahosted.org/freeipa/ticket/607 has been opened on FreeIPA to track the issue.

The problem is server-side. Using nsupdate directly when dealing with AAAA records fails, so it's not related to SSSD's usage.

coverity: =>
resolution: => invalid
status: assigned => closed

Fields changed

rhbz: => 0

Metadata Update from @sgallagh:
- Issue assigned to sgallagh
- Issue set to the milestone: SSSD 1.5.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/1743

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.
Metadata
None
None
None
Highest
0
defect
IPA Provider
master
0
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.