IPAM subnet reconciliation: partial coverage
The gap in the alibi. Find the gap before approving the allocation.
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: Compare observed routed prefixes with IPAM allocation records in the same routing context.
Validation: Fictional reconciliation lab; not a live network diagnosis. 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
Compare the observed routed prefixes with the IPAM allocation, retaining routing context and collection scope. A partial routing snapshot is not permission to delete an allocation.
Checks to compare
- Confirm prefix boundaries and the parent allocation.
- Check whether observed subnets overlap or leave gaps.
- Validate the routing domain, inventory source and collection time.
Reveal the finding and next action
The observed prefixes cover only part of the allocation; the unexplained space requires more evidence.
Document the coverage evidence, retain ownership information and investigate unexplained gaps before changing the source of truth.