Comment 16 for bug 1872118

I don't have specific recommendation on this.

The best course of action would be to find a new maintainer that would update the packages to 4.4.2. The upstream (ISC) does very infrequent releases. We had 4.4.2 coming out in Jan 2020. We don't know when the next one (4.4.3) will come out, but we're no longer actively developing it. We're fixing serious bugs reported by customers (and addressing security issues if found), so the future releases are driven by that.

My point here is that this isn't that much work to do. Perhaps existing maintainers could be convinced to do the package updates?

Also, the alternative - ISC Kea - is much superior in many regards. It's modern, can (but doesn't have to) use MySQL, Postgres and other databases, has much better performance, is extensible with hooks, much cleaner configuration using JSON, ability to alter almost every aspect of its configuration during runtime, the dev version already support multi-threading etc. This is the ultimate solution to that problem: migrate to Kea and stop using isc-dhcp altogether.

Finally, ISC provides packages for Kea for many systems, including Ubuntu. We can work with package maintainers if there are specific patches that are needed. We don't and we don't be able to do that for isc-dhcp.