[Freeipa-users] sssd not updating reverse dns

[Sigbjorn Lie]

On 11/13/2011 02:49 PM, Simo Sorce wrote:
> On Sat, 2011-11-12 at 16:10 +0100, Sigbjorn Lie wrote:
>> On 11/12/2011 03:55 PM, Sigbjorn Lie wrote:
>>> Hi,
>>>
>>> I notice that when sssd is configured to update DNS, it's only
>>> updating the DNS forward zone, it's not updating the DNS reverse zone.
>>> And I cannot find any option for enabling updating of the reverse dns
>>> zone.
>>>
>>> Have I missed something? Or is updating the reverse zone not supported?
>>>
>>>
>>>
>> When I restarted SSSD on one of the clients, named crashed on one of my
>> ipa servers with the output below in the messages log file.
>>
>>
>> Nov 12 16:01:02 ipa01 named[2770]: client
>> 2021:472:dcdd:10:a00:27ff:fe0c:8283#55995: updating zone
>> 'ix.test.com/IN': deleting rrset at 'client8.ix.test.com' A
>> Nov 12 16:01:03 ipa01 named[2770]: zone ix.test.com/IN: sending notifies
>> (serial 2012)
>> Nov 12 16:01:03 ipa01 named[2770]: client
>> 2021:472:dcdd:10:a00:27ff:fe0c:8283#44246: updating zone
>> 'ix.test.com/IN': deleting rrset at 'client8.ix.test.com' AAAA
>> Nov 12 16:01:03 ipa01 named[2770]: client
>> 2021:472:dcdd:10:a00:27ff:fe0c:8283#39501: updating zone
>> 'ix.test.com/IN': adding an RR at 'client8.ix.test.com' A
>> Nov 12 16:01:03 ipa01 named[2770]: rdata.c:814: REQUIRE(rdata != ((void
>> *)0)) failed, back trace
>> Nov 12 16:01:03 ipa01 named[2770]: #0 0x7f3cc069145b in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #1 0x7f3cbe9426da in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #2 0x7f3cbff607ad in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #3 0x7f3cba5cf218 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #4 0x7f3cba5d2fe0 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #5 0x7f3cba5cd758 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #6 0x7f3cbfee502b in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #7 0x7f3cc06af84d in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #8 0x7f3cc06b4824 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #9 0x7f3cbe9618c8 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #10 0x7f3cbe318b31 in ??
>> Nov 12 16:01:03 ipa01 named[2770]: #11 0x7f3cbd860d2d in ??
>> Nov 12 16:01:03 ipa01 named[2770]: exiting (due to assertion failure)
>> Nov 12 16:01:03 ipa01 systemd[1]: named.service: main process exited,
>> code=killed, status=6
>> Nov 12 16:04:50 ipa01 systemd[1]: Unit named.service entered failed state.
> Can you please install debuginfo packages for named and bind-dyndb-ldap,
> reproduce and open a bug agains the bind-dyndb-ldap component. We'll
> want to fix this issue ASAP.
>
> Simo.
>

Ok, I've done that. I will let you know if/when it happens again.

I also noticed that the "ipactl status" command still displayed: "DNS 
Service: RUNNING", even though the DNS service was crashed.


Rgds,
Siggi