I already posted my dnsmasq "solution" so I will skip this. If you want a code example I could whip you one up.
Then there is coredhcp [1] and you can write plugins written in go for it.
From time to time some hobby dhcp server pop up, but most fade away since (I guess) the existing solutions are "good enough". I for instance implement a automatic provisioning and configurating dhcp setup with tftp and pxe boot using dnsmasq. It automatically creates pxe configs based on the mac address and some other stuff (tm). Kea seemed overkill for this usecase and I'm quite happy with what I got.
Your use case of automatically fixing hostnames through ISC seems a bit overkill to me as well to be frank. My home network has a few VLANs and every device in it is managed manually. It's a one time setup and most automation is unnecessary (and some devices in my network flatout ignore some dhcp options....). Aaaaanyway I still think that most dhcp servers out there support some form of scripting (heck even udhcpcd has a lease notify script that could be hacked to offer some of that functionality even though this gets only executed after the fact so a bit useless [2]).
> oh wait, I wonder how much ISC was paid … to do exactly this EOL … by these major ISPs?
I don't know. Nothing?
> Plausible future: I can envision a special DHCP vendor-specific OPTION to use time-based blockchain hash to further solidify their hold.
Reading your cynic banter I'm quite happy of not having your DHCP problems. Looking through your github repositories I can find a bunch of configuration files for dhclient, but not much in form of ISC configs (only the nintendo fix you posted in your first post). Would be really interested in your setup.
[0] https://kea.readthedocs.io/en/latest/arm/hooks.html
[1] https://github.com/coredhcp/coredhcp
[2] https://github.com/mirror/busybox/blob/master/examples/udhcp...
Good writeup. Great re-starting point after my 5-year hiatus.
These wannabes have all fallen short and this will remain a problem for as long as many of those top-15 ISPs continues to use these esoteric settings of Juniper Network for their custom Network Management System (NMS) and in-house provisioning setups.
All of those Wannabe DHCP server replacements are an expensive proposition in terms of time, money, and resources.
Mostly likely, this will further solidify the deployment of ISPs’ in-house gateway boxes thus preventing any custom gateways from replacing them.
oh wait, I wonder how much ISC was paid … to do exactly this EOL … by these major ISPs?
Plausible future: I can envision a special DHCP vendor-specific OPTION to use time-based blockchain hash to further solidify their in-house gateway deployment hold.