<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">If I’m reading logs correctly, your BIND nameserver is rejecting the update as the Kea request is requiring NXRRSET (means the record cannot already exist in the nameserver). I don’t see Kea config option to change that behavior. By chance did you manually create the PTR record for 74.10.168.192.in-addr.arpa in you BIND zone outside of Kea? If so, might try removing it. I don’t have any personal experience w/ Kea updating reverse records but g<span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);">uessing that at least w/ PTR records, Kea will not update if record already exists. </span><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br></span></font></div><div><font color="#000000"><span style="caret-color: rgb(0, 0, 0);"><br id="lineBreakAtBeginningOfMessage"></span></font><div><br><blockquote type="cite"><div>On Jan 28, 2024, at 12:51, Ubence Quevedo (thatrat) <thatrat@gmail.com> wrote:</div><br class="Apple-interchange-newline"><div><meta http-equiv="content-type" content="text/html; charset=utf-8"><div style="overflow-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;">Thanks for the response, I took a look at the ddns log file I have setup on my bind 9 server and found the following:<div><div><font face="Courier New">27-Jan-2024 15:55:15.083 update: info: client @0xffff7c339b18 192.168.10.3#50944/key ddns-key: updating zone 'totusmel.com/IN': deleting an RR at lg-washer.totusmel.com A</font></div><div><font face="Courier New">27-Jan-2024 15:55:15.123 update: info: client @0xffff6c2c4228 192.168.10.3#56549/key ddns-key: updating zone 'totusmel.com/IN': delete all rrsets from name 'lg-washer.totusmel.com'</font></div><div><font face="Courier New">27-Jan-2024 15:55:15.143 update: info: client @0xffff702ec848 192.168.10.3#34817/key ddns-key: updating zone '10.168.192.in-addr.arpa/IN': update unsuccessful: 74.10.168.192.in-addr.arpa/PTR: 'RRset exists (value dependent)' prerequisite not satisfied (NXRRSET)</font></div></div><div><br></div><div>It seems to be the same output as journalctl but through bind’s terminology.<br id="lineBreakAtBeginningOfMessage"><div><br></div><div>I’m pretty sure the forward zone is getting updated properly since there’s a .jnl file and the serial number in the zone file is incrementing.</div><div><br></div><div>For some reason, the below section got stripped out in the response:</div><div><div style="caret-color: rgb(0, 0, 0);">The relevant section from the kea-dhcp4.conf:</div><div style="caret-color: rgb(0, 0, 0);"><div><font face="Courier New"> "dhcp-ddns": {</font></div><div><font face="Courier New"> "enable-updates": true</font></div><div><font face="Courier New"> }</font></div><div><font face="Courier New"> "ddns-qualifying-suffix": "<a href="http://totusmel.com/">totusmel.com</a>",</font></div><div><font face="Courier New"> "ddns-override-client-update": true,</font></div></div></div><div><br></div><div>Do I also need to add reverse zone 10.168.192.in-addr.arpa to the kea-dhcp4.conf?</div><div><br></div><div>Any other thoughts or comments on this would be appreciated!</div><div><br></div><div>-Ubence</div><div><br></div></div></div></div></blockquote></div><br></div></body></html>