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

Detect an unauthorised DHCP server

The intermittent DHCP lottery. Users on one floor occasionally get the wrong gateway and lose access to internal services. A reconnect sometimes fixes it. The official DHCP dashboard sees no failures. It is only monitoring the official server.

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: Synthetic VLAN 88. Only DHCP server 10.99.0.10 is authorised. A misplaced lab router is attached to the same broadcast domain.

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

Users on one floor occasionally get the wrong gateway and lose access to internal services. A reconnect sometimes fixes it. The official DHCP dashboard sees no failures. It is only monitoring the official server.

Checks to compare

  1. Capture one full lease exchange. Compare what this check establishes with the other devices in the path.
  2. Trace the unexpected responder. Compare what this check establishes with the other devices in the path.
  3. Simulate controlled containment. Compare what this check establishes with the other devices in the path.

Scope matters. Synthetic VLAN 88. Only DHCP server 10.99.0.10 is authorised. A misplaced lab router is attached to the same broadcast domain.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

The capture links the bad settings to an acknowledged lease from the unauthorised router. MAC tracing identifies its attachment, and lab containment removes the competing offer.

Common mistakes to avoid in this scenario

  • Official pool too small: Expand the official scope.
  • Authoritative DNS record missing: Create an A record for the default gateway.

A proportionate next action

Contain the confirmed responder without disrupting unrelated devices. Renew affected clients through the approved service and consider correctly scoped DHCP snooping.

Limits of the conclusion

Multiple offers are not inherently rogue: authorised redundancy may produce them. Inventory, policy and selected-server evidence establish the problem here.

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