Troubleshoot DHCP relay helper addresses
The relay to nowhere. A new VLAN has no DHCP leases. The server has a matching pool and plenty of free space. A router configuration was copied from another site. Nobody remembers which one.
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: VLAN 70, gateway 10.70.0.1. Authorised DHCP server 10.99.0.10. The obsolete server address is retired.
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
A new VLAN has no DHCP leases. The server has a matching pool and plenty of free space. A router configuration was copied from another site. Nobody remembers which one.
Checks to compare
- Capture on client VLAN. Compare what this check establishes with the other devices in the path.
- Inspect relay configuration. Compare what this check establishes with the other devices in the path.
- Simulate approved correction. Compare what this check establishes with the other devices in the path.
Scope matters. VLAN 70, gateway 10.70.0.1. Authorised DHCP server 10.99.0.10. The obsolete server address is retired.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The relay forwards DHCP requests to a retired server, so the authorised server cannot respond. The lab correction restores the full exchange.
Common mistakes to avoid in this scenario
- Scope exhaustion: Make the pool larger.
- DNS record missing: Create an A record for the laptop.
A proportionate next action
Correct the destination after approval, preserve intended relay context and verify DORA on the client and server sides.
Limits of the conclusion
No offer alone does not identify the fault. Captures, configuration and the controlled lab test establish the cause.