Your questions and comments make me think you misunderstand the role of a DHCP server in the context of Active Directory.
A "free" DHCP server, open source or not, doesn't make Active Directory work. DNS, with appropriate entries in the zone files, is FAR more important in "making AD work" than is DHCP.
Worst comes to worst, you can statically configure all your hosts on a network and have AD work properly with a correctly configured DNS server. DHCP is for ease of use and automation, in contrast.
Your goal seems to be to have a backup for your Active Directory Domain Controller, without spending another $700 for a Windows Server license. You can't get there from here.
You should have a DC on each of two physical servers as a best practice for fault tolerance and redundancy. When I say physical, I really mean the DC's should be virtual machines on a hypervisor host, two each. I haven't run DC's on bare metal in a decade, but even my test environment has two DC VM's.
I wish you well on your project, but the task and constraints you describe make it a no-go in my view.
1 found this helpful
thumb_up
thumb_down