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.
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
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
- Capture one full lease exchange. Compare what this check establishes with the other devices in the path.
- Trace the unexpected responder. Compare what this check establishes with the other devices in the path.
- 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.