#2783 REGRESSION: Dyndns soes not update reverse DNS records
Closed: Fixed None Opened 6 years ago by lslebodn.

Downstream tests are failing for updating reverse DNS records.

:: [   FAIL   ] :: default_reverse (Expected 0, got 1)
:: [   FAIL   ] :: RESULT: default
:: [   FAIL   ] :: ttl_reverse (Expected 0, got 1)
:: [   FAIL   ] :: RESULT: ttl
:: [   FAIL   ] :: force_tcp_unblocked_reverse (Expected 0, got 1)
:: [   FAIL   ] :: RESULT: force_tcp
:: [   FAIL   ] :: RESULT: /CoreOS/sssd/client/ad_provider/dyndns/root

git bisect says that it was introduced by commit

b0a8ed519554f8896e35812e0759862c33f157fe is the first bad commit
commit b0a8ed519554f8896e35812e0759862c33f157fe
Author: Pavel Reichl <preichl@redhat.com>
Date:   Tue Jul 14 09:56:59 2015 -0400

    DYNDNS: support for dualstack

    When dyndns_iface option was not used, address of connection to LDAP
    was used. This patch proposes following change:
      * Interface containing address of connection is found.
      * All A and AAAA addresses of this interface are collected.
      * Collected addresses are sent during DDNS update.
      * Function sss_iface_addr_add() is removed.


Fields changed

owner: somebody => preichl

Fields changed

resolution: => invalid
status: new => closed

The ticket should be still opened. We need to track it. Until it will be solved in nsupdate. If it will not be possible to fix nsupdate in short time frame then we will need to change behaviour of sssd (at least for ad provider)

resolution: invalid =>
status: closed => reopened

OK, it's not possible to fix nsupdate apparently. We need to send nsupdate separately for each update, then...

I have the patch, but it's not easy to back port it to prev. version. It also seems now that even nsupdate has patch (https://bugzilla.redhat.com/show_bug.cgi?id=1262430).

Fields changed

patch: 0 => 1

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.13.1

resolution: => fixed
status: reopened => closed

Metadata Update from @lslebodn:
- Issue assigned to preichl
- Issue set to the milestone: SSSD 1.13.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/3824

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.