It works for me, and I’ve been managing DNS/DHCP for 35 years!
Keep a very small DHCP Pool. I use 241-254 for ALL clients. That’s more than enough.
DHCP does NOT make entries in DNS. I do NOT have use for this function, which is a source of bad planning / lazyness!
All Servers, NAS, Printers have a static IP in my Networks - but also a reservation for the same IP as DHCP (manually). I do this because often I’ve seen printers “lose their memory - or config” after updating, and they switch back to DHCP. This way, I get it right, even if I have to setup a server or printer anew - the IP is correct.
If you MUST use DHCP -> DNS, switch it off before changing anything, but YMMV…
I do prefer good or even better planning!
For me, this is a non issue!
I have more issues with the DNS in NethServer not able to handle: CNAMEs, PTRs or MX / NS entries… But I can handle that with OPNsense…
My 2 cents