Troubleshoot DHCP Option 82 policy mismatches
The security upgrade that broke renewals. After an access-network security rollout, one group of customers cannot renew. Other customers on the same server still obtain leases. The change ticket says ‘visibility improvement’. Visibility into complaints has certainly improved.
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: A synthetic Option 82 policy mismatch. One access circuit changed its circuit-ID format. Relay destination, giaddr and pool mapping are otherwise correct.
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
After an access-network security rollout, one group of customers cannot renew. Other customers on the same server still obtain leases. The change ticket says ‘visibility improvement’. Visibility into complaints has certainly improved.
Checks to compare
- Compare packet captures. Compare what this check establishes with the other devices in the path.
- Inspect policy decision log. Compare what this check establishes with the other devices in the path.
- Simulate a reviewed mapping change. Compare what this check establishes with the other devices in the path.
Scope matters. A synthetic Option 82 policy mismatch. One access circuit changed its circuit-ID format. Relay destination, giaddr and pool mapping are otherwise correct.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The server receives the request and explicitly rejects its new circuit-ID representation. A controlled mapping correction resolves this lab incident. The metadata is not intrinsically invalid just because its format changed.
Common mistakes to avoid in this scenario
- Pool exhaustion: Increase the lease pool.
- Option 82 is universally incompatible: Disable it across all access switches.
A proportionate next action
Compare relay metadata end to end, establish which insertion point is authoritative and correct the narrow policy mismatch. Preserve trust boundaries.
Limits of the conclusion
The linked discussion is inspiration, not a verified diagnosis of this fictional incident. Real Option 82 problems can involve trust settings, nested relays or server behaviour.