DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DHCP · Advanced

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.

DDIENGINEER.COM / INTERACTIVE NETWORK INVESTIGATIONS

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.

ADVANCED · DNS + DHCP · ~8 MIN

Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.

01 Inspect the clues02 Build your theory03 Make the call
FEATURED / PD–009DNS + DHCP
THE LAPTOP WITH YESTERDAY’S ADDRESS

New lease.
Old address.
Same confused user.

09:30 / DHCP ACK10.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.

FIELD NOTES / READ BEFORE OR AFTER THE LAB

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

  1. Compare both configurations. Compare what this check establishes with the other devices in the path.
  2. Inspect replication timeline. Compare what this check establishes with the other devices in the path.
  3. 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.

Read the technical reference →

Browse all investigations →

Browse troubleshooting case guides →The missing networkThe gap in the alibiThe record that refused to existThe name with two addressesThe office with no vacanciesThe relay to nowhereThe duplicate that wasn’tThe suspiciously quiet subnetThe laptop with yesterday’s addressThe security upgrade that broke renewalsThe container that couldn’t find anythingThe lease that rewrote historyThe intermittent DHCP lotteryThe edit that never reached DNSThe policy inherited from upstairsThe updater with the wrong badgeThe fixed address with no nameThe duplicate in another network viewThe update at the wrong front doorThe lease with no permission slipThe reservation the partner forgotThe immortal DNS recordThe pipeline that retried yesterdayThe route that outlived its resolverThe adjacency with no routeThe domain controller nobody could findThe backup with a missing keyThe green dashboard with the wrong answerThe two masters of one recordThe zone transfer with no guest listThe inventory that stopped at page oneThe allocation raceThe redundant pair on one plugThe answer too large for the doorThe IPv6 address with nowhere to go