troubleshooting Question
DHCP leases not syncing between two DCs
asked on
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.
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.
Learn from the best
Network and collaborate with thousands of CTOs, CISOs, and IT Pros rooting for you and your success.
Andrew Hancock - VMware vExpert
See if this solution works for you by signing up for a 7 day free trial.
Unlock 2 Answers and 4 Comments.
Try for 7 days”The time we save is the biggest benefit of E-E to our team. What could take multiple guys 2 hours or more each to find is accessed in around 15 minutes on Experts Exchange.
Our community of experts have been thoroughly vetted for their expertise and industry experience.
The Distinguished Expert awards are presented to the top veteran and rookie experts to earn the most points in the top 50 topics.