Red Hat Bugzilla – Bug 1187146
If v4 address exists, will not create nonexistant v6 in ipa domain
Last modified: 2015-11-19 06:35:37 EST
Description of problem: On a dual ipv4/ipv6 system, both with valid addresses. At initial install, IPA / sssd only creates the v4 record. After the install, sssd attempts a DNS update. The following is logged. [sdap_dyndns_dns_addrs_done] (0x0400): No DNS update needed, addresses did not change [ipa_dyndns_nsupdate_done] (0x0040): DNS update finished However, only the A record exists, the AAAA does not. As a result, the AAAA is never updated. Deleting the IPV4 record and restarting SSSD yields: [sdap_dyndns_dns_addrs_done] (0x0400): Detected IP addresses change, will perform an update [be_nsupdate_create_fwd_msg] (0x0400): -- Begin nsupdate message -- realm EXAMPLE.COM zone example.com. update delete yvett.example.com. in A send update delete yvett.example.com. in AAAA send update add yvett.example.com. 1200 in A 172.24.11.24 send [be_nsupdate_create_fwd_msg] (0x0400): -- End nsupdate message -- [write_pipe_handler] (0x0400): All data has been sent! [sdap_dyndns_update_done] (0x0400): No PTR update requested, done [ipa_dyndns_nsupdate_done] (0x0040): DNS update finished However, only the v4 record is created. No PTR or AAAA is created. (This may be a different issue). Therfore delete / recreate is not a work around. Version-Release number of selected component (if applicable): sssd-client-1.11.2-68.el7_0.6.x86_64 freeipa-3.3.5 How reproducible: Always
Correction: Only the AAAA is not updated. The PTR is created.
At the moment, this is "expected". By default, we only update with the address that is read from the socket connecting to the LDAP server. The only alternative now is to specify the interface to update the addresses from. We're aware this is suboptimal and we're planning to address this issue upstream, currently in the 1.13 milestone. I'll link this bugzilla with the upstream ticket.
Upstream ticket: https://fedorahosted.org/sssd/ticket/2120
IE the work around is to provide: dyndns_iface = eth0 And it will update A and AAAA? I am going to try this as well. Perhaps this should be documented?
zone example.com. update delete yvett.example.com. in A send update delete yvett.example.com. in AAAA send update add yvett.example.com. 1200 in AAAA 2001:db8:0:11:5054:ff:feba:574 update add yvett.example.com. 1200 in A 172.24.11.24 send This works correctly as a work around. Thanks.
Upstream ticket: https://fedorahosted.org/sssd/ticket/2558
* b0a8ed519554f8896e35812e0759862c33f157fe * 1112e84494bcfd0f658e073d25f15ed877d047aa * 0a26e92fb2a4dd9704a0578f90241997e2aed269 * 038b9ba28a618e3e553803da632116a040b94034 * aa3fd6fde3888c0e333cad852ae5b4f671d55f58
Created attachment 1083204 [details] log Verfied sssd-1.13.0-39.el7.x86_64 install update ok sssd update ok PTR must be enabled to get it updated
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHSA-2015-2355.html