DHCP leases not syncing between two DCs

I relatively recently demoted one of our two 2008 domain controller, and added a 2016 DC. We'll call them DC1 (2008) and DC2 (2016).

AD, DNS, DHCP (To an extent) have been fine...but I noticed today that nslookup is searching DC1 and returning "Can't find...".

I went into both DC's and they do not share each others DHCP leases. DC1 has some, and DC2 has the others. I've been fortunate not to have a duplicate address leased, but I'd like to get this straightened out before one is.

Is there a compatibility issue between 2008 and 2016 DHCP i overlooked? I'm not able to set a failover in 2016 to anything less than a 2012 DHCP server.
Who is Participating?
Cliff GaliherCommented:
The easiest solution is to split the scope among the servers. Set different exclusion ranges on each to essentially make the addresses each server cam hand out unique. 80/20 and 50/50 are common ratios.
Cliff GaliherCommented:
DHCP has *never* synced leases via AD.

In 2012, DHCP failover was introduced, but doesn't use AD and requires specific steps to set up. You can't use 2008 for it.
RISLAAuthor Commented:
Is there anything I can do to ensure they're not putting out the same addresses? It sounds like they don't communicate like I assumed.
RISLAAuthor Commented:
Thank you. I have a lot to learn about older OS's!
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.