Where do I configure the failover partner?

You don’t. The DHCP code has no failover partner and no split scope. Lease rows are in Postgres.

Can two dhcpd processes share the leases?

Yes. The allocator is a Postgres store that any number of processes can call. Each lease row records the node that wrote it.

Will this node answer a request meant for another server?

No. A Request whose server identifier is a different address is ignored. The reply this process sends uses its own server address.

Lattice

Notes

There is no DHCP failover partner (and no split scope)

Lattice has no Windows DHCP failover partner and no split scope. Lease rows live in Postgres, and any number of dhcpd processes can write them.

Oct 28, 2026 · Query: DHCP failover partner split scope

There is nothing to set up and no split scope to import, because the DHCP code has neither.

A lease is a row in Postgres. The allocator is written so any number of dhcpd processes can call it, and the row stores the node that granted it. There is no partner relationship to keep in sync, and no second scope that owns half the addresses.

A Request that names a different server identifier is ignored. When this process does reply, it uses its own server address as the server identifier.

FAQ

Where do I configure the failover partner?: You don’t. The DHCP code has no failover partner and no split scope. Lease rows are in Postgres. HA.
Can two dhcpd processes share the leases?: Yes. The allocator is a Postgres store that any number of processes can call. Each lease row records the node that wrote it.
Will this node answer a request meant for another server?: No. A Request whose server identifier is a different address is ignored. The reply this process sends uses its own server address. HA.

Replace Windows DHCP Create an account Install