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

Diagnose DHCP pool exhaustion

The office with no vacancies. New laptops cannot get an address. Existing laptops continue working. The DHCP service dashboard is green. The dashboard would like that entered into the record.

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: Single authorised server; VLAN 40. Client requests reach the server. No failover partner or alternative pool in this lab.

Validation: Fictional training scenario; not vendor-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

New laptops cannot get an address. Existing laptops continue working. The DHCP service dashboard is green. The dashboard would like that entered into the record.

Checks to compare

  1. Trace a new client request. Compare what this check establishes with the other devices in the path.
  2. Audit the pool. Compare what this check establishes with the other devices in the path.
  3. Review safe capacity options. Compare what this check establishes with the other devices in the path.

Scope matters. Single authorised server; VLAN 40. Client requests reach the server. No failover partner or alternative pool in this lab.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

The 50-address pool is entirely unavailable: 48 active leases plus two conflict-marked addresses. The server receives requests but cannot allocate an address.

Common mistakes to avoid in this scenario

  • Broken relay: Change helper address.
  • Leases are disposable: Delete every active lease.

A proportionate next action

Investigate conflicts and validate capacity before changing the pool. Do not erase active leases or blindly extend into unverified addresses.

Limits of the conclusion

A /24 does not mean 254 dynamic leases are configured. Scope range, exclusions and lease state matter.

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