<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;">Depending upon the version and configuration, your prior version of ISC dhcpd likely did not use DHCID records. The legacy ISC dhcpd could use TXT records or none. See <a href="https://kb.isc.org/docs/aa-01091">https://kb.isc.org/docs/aa-01091</a> <div>Guessing your prior running dhcpd was only updating the PTR record for reverse updates in past.<br><div><br id="lineBreakAtBeginningOfMessage"><div><br><blockquote type="cite"><div>On Jan 28, 2024, at 21:42, 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;">So, I think the <font face="Courier New">ANY</font> in the update policy worked in the reverse zone?<div><br></div><div>I’m not getting errors any longer and the zone file is getting populated with records similar to how the main zone is.</div><div><br></div><div>Previously in the reverse zone with how things were configured, there weren’t and <font face="Courier New">DHCID</font> records, but there are now.</div><div><br></div><div>I still find it bizarre that it worked perfectly with PTR before but only seems to work with ANY in the zone update-policy definition.</div><div><br></div><div>-Ubence<br id="lineBreakAtBeginningOfMessage"><div><br></div></div></div></div></blockquote></div><br></div></div></body></html>