Hello,
Please test the following method to see if it solves the problem:
Verify that DHCID records are generated correctly on non-Windows clients, and ensure that IPv4 and IPv6 DHCID records are consistent.
Adjust the dynamic update Settings for DNS zones to allow for a more relaxed update policy (subject to security risks).
Configure on a DHCP server to force the handling of DHCID on non-Windows clients, for example through policy or advanced Settings.
Contact the vendor of non-Windows devices to verify that their DHCP client implementation is RFC compliant, especially for DHCID processing in a dual-stack environment.
For some critical non-Windows devices, consider manually creating static A records and AAAA records on the DNS server to avoid registration issues caused by DHCP name protection.
I hope the information above is helpful.
Best regards
Zunhui
============================================
If the Answer is helpful, please click "Accept Answer" and upvote it.