Troubleshoot Windows DHCP failover configuration replication
The reservation the partner forgot. A client gets its reserved address from DHCP-A but a different address when DHCP-B responds. The service dashboard is green. It would like credit for trying.
What you’ll practise
Inspect the supplied evidence, distinguish competing explanations and choose a proportionate next action. Use the clickable topology and private notebook to keep track of your findings.
Lab scope: Documentation-based fictional lab. No appliance/build reproduction claimed. ddiengineer.com names are simulated, not live DNS.
Validation: Documentation-based fictional lab; not build-verified. No live network access is required. Basic DNS, DHCP and IP addressing knowledge is helpful. Progress is stored in this browser.
DHCP says yes.
DNS says yesterday.
A laptop moved networks. Its name didn’t. Find out who’s telling the truth — and what you should check next.
Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.
New lease.
Old address.
Same confused user.
10.62.4.27 ✓↓ six minutes and three cache flushes later09:36 / DNS ANSWER10.61.4.27 ?“Have you tried flushing it again?”
The fourth time is not a strategy.
Troubleshooting guide
Recognise the symptoms
A client gets its reserved address from DHCP-A but a different address when DHCP-B responds. The service dashboard is green. It would like credit for trying.
Checks to compare
- Compare both configurations. Compare what this check establishes with the other devices in the path.
- Inspect replication timeline. Compare what this check establishes with the other devices in the path.
- Verify controlled replication. Compare what this check establishes with the other devices in the path.
Scope matters. Documentation-based fictional lab. No appliance/build reproduction claimed. ddiengineer.com names are simulated, not live DNS.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
Lease-state communication is working. No scope-configuration replication occurred after the reservation edit. Reviewed scope replication from the intended source aligns both partners. Controlled client test confirms settings.
Common mistakes to avoid in this scenario
- Client changed identity: The captured client identifier is the same on both exchanges.
- Restart every DDI service: No evidence supports a broad restart.
A proportionate next action
Replicate the intended scope configuration in the correct direction and verify partner state.
Limits of the conclusion
Configuration replication and lease-state exchange are distinct. Lab follows documented Windows Server workflow; exact builds remain unspecified.