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 https://kb.isc.org/docs/aa-01091 Guessing your prior running dhcpd was only updating the PTR record for reverse updates in past.
> On Jan 28, 2024, at 21:42, Ubence Quevedo (thatrat) <[email protected]> wrote: > > So, I think the ANY in the update policy worked in the reverse zone? > > I’m not getting errors any longer and the zone file is getting populated with > records similar to how the main zone is. > > Previously in the reverse zone with how things were configured, there weren’t > and DHCID records, but there are now. > > 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. > > -Ubence >
-- ISC funds the development of this software with paid support subscriptions. Contact us at https://www.isc.org/contact/ for more information. To unsubscribe visit https://lists.isc.org/mailman/listinfo/kea-users. Kea-users mailing list [email protected] https://lists.isc.org/mailman/listinfo/kea-users
