DHCP client names not configurable and result in dynamic DNS update failures
I'm running a mesh with 6 nodes in AP mode where the Ip addresses are obtained from a Windows Server DHCP instance.
However when the lease is requested, the units pass the default name "Deco-BE85" to the DHCP server.
When dynamic updates are then requested to the DNS server, since this is configured to reject duplicate names, the result is only one of the Deco units is ever registered.
Even if the leases are converted to reservations at the DHCP server, this is not workable since on every Deco reboot, the client name passed from the Deco units is again "Deco-BE85" and the same issue results again.
The simple request is to be able to configure the Deco unit names, or failing that, do something similar to other IOT devices which is to pass the MAC address along with the model name as a unique string.
