[Kea-users] DDNS subsequent failure after successful CHG_ADD

[MRob]

> I just commented on your other thread.

Thank you, our version of pdns is quite old (from repo) so I hope 
upgrading it is the solution. I will report back.

> Does the PDNS record you are
> trying to update already exist, and does the DHCID record match the
> one in the PDNS records?

Yes, the first CHG_ADD has populated DHCID and correct forward and 
reverse entries. Thats why I ask, maybe I can ignore this error. I 
wasn't sure if setting override-*-update was too aggressive


>> Initial forward and reverse DNSUPDATE commands succeed:
>> 
>> DHCP_DDNS_ADD_SUCCEEDED DHCP_DDNS Request ID xxx: successfully added
>> the
>> DNS mapping addition for this request: Type: 0 (CHG_ADD)
>> 
>> But Kea does another CHG_ADD only a minute later and it fails:
>> 
>> DHCP_DDNS_FORWARD_REPLACE_REJECTED DNS Request ID yyy: Server,
>> 10.10.1.254 port:5353, rejected a DNS update request to replace the
>> address mapping for FQDN, wkst7.lan., with an RCODE: 8
>> DHCP_DDNS_ADD_FAILED DHCP_DDNS Request ID yyy: Transaction outcome
>> Status: Failed, Event: UPDATE_FAILED_EVT,  Forward change: failed,
>> Reverse change: failed,  request: Type: 0 (CHG_ADD)
>> 
>> Is this a problem or can it be ignored? Is it due to setting
>> "override-no-update": true and "override-client-update": true?
>> _______________________________________________
>> Kea-users mailing list
>> Kea-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/kea-users