2 ms·

Powerdns and dnsdist are incredible projects with a lot of features. Dnsdist has particularly added a lot of flexibility with ebpf/lua support. Shameless plug

Powerdns and dnsdist are incredible projects with a lot of features. Dnsdist has particularly added a lot of flexibility with ebpf/lua support. Shameless plug in related space that I was able to get open sourced is Dora a rust written DHCP server. https://github.com/bluecatengineering/dora https://github.com/bluecatengineering/dora Disclaimer: Opinions mine. Work at a DNS, DHCP, IPAM company.

sofixa 3y ago
Finally a good looking new entrant in the DHCP space. There's a severe lack of good quality modern DHCP software (as in, there's a usable API available, easy to scale and make redundant, etc.). Good luck with the project!
- jesterson 3y ago
  Sorry to jump in, what do you mean under "severe lack of good quality modern DHCP software"? There is no shortage of amazingly reliable DHCP servers that work for many years without restarts. It's an old, well tested reliable technology, that just works. What "modern" stuff you would like to bring?
  - sofixa 3y ago
    That's why I elaborated. I want(ed, it was at a previous job) a DHCP server that has a good usable API (so not the sorry excuse that isc-dhcp-server has), works reliably (isc-dhcp-server is not reliable in HA mode), allows for easy custom integrations/plugins/hooks to third-party systems (recompiling C++ projects is not it, cough Kea). Basically like CoreDNS, but for DHCP. What we do have is isc-dhcp-server (obsolete technically, horrific "API" that is downright unusable), Kea (made from the same people, better but much heavier, and plugins are in C++ so need recompiling with lack of documentation around it; API is pretty bad too), and Windows DHCP which I'm not sure even has an API, but it doesn't matter anyways because nobody sane would run Windows just for DHCP. Am I missing anything? The scenario was as follows: DHCP server that needs to run in HA across multiple DCs, have an API that allows for stuff such as setting reservations based on leases (necessary with isc-dhcp-server because leases aren't shared between an HA pair, really, so if the "wrong" one answers the IP can change), but also querying list of leases by MAC, etc. etc. Also, being able to easily say reliably run this script/plugin after each lease/reservation so that it can be registered in other systems such as IPAM, monitoring, inventory, etc. etc. Neither isc-dhcp-server nor it's replacement Kea really cut it.

sofixa 3y ago

Finally a good looking new entrant in the DHCP space. There's a severe lack of good quality modern DHCP software (as in, there's a usable API available, easy to scale and make redundant, etc.). Good luck with the project!

jesterson 3y ago
Sorry to jump in, what do you mean under "severe lack of good quality modern DHCP software"? There is no shortage of amazingly reliable DHCP servers that work for many years without restarts. It's an old, well tested reliable technology, that just works. What "modern" stuff you would like to bring?
- sofixa 3y ago
  That's why I elaborated. I want(ed, it was at a previous job) a DHCP server that has a good usable API (so not the sorry excuse that isc-dhcp-server has), works reliably (isc-dhcp-server is not reliable in HA mode), allows for easy custom integrations/plugins/hooks to third-party systems (recompiling C++ projects is not it, cough Kea). Basically like CoreDNS, but for DHCP. What we do have is isc-dhcp-server (obsolete technically, horrific "API" that is downright unusable), Kea (made from the same people, better but much heavier, and plugins are in C++ so need recompiling with lack of documentation around it; API is pretty bad too), and Windows DHCP which I'm not sure even has an API, but it doesn't matter anyways because nobody sane would run Windows just for DHCP. Am I missing anything? The scenario was as follows: DHCP server that needs to run in HA across multiple DCs, have an API that allows for stuff such as setting reservations based on leases (necessary with isc-dhcp-server because leases aren't shared between an HA pair, really, so if the "wrong" one answers the IP can change), but also querying list of leases by MAC, etc. etc. Also, being able to easily say reliably run this script/plugin after each lease/reservation so that it can be registered in other systems such as IPAM, monitoring, inventory, etc. etc. Neither isc-dhcp-server nor it's replacement Kea really cut it.