Review inactive and reserved IPAM subnets
The suspiciously quiet subnet. Discovery shows no active hosts in 10.90.5.0/24 for seven days. Someone marks it “free”. The disaster recovery team has not yet been invited to this conversation.
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: IPAM allocation status is reserved. Discovery records show only observed activity, not business ownership.
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
Discovery shows no active hosts in 10.90.5.0/24 for seven days. Someone marks it “free”. The disaster recovery team has not yet been invited to this conversation.
Checks to compare
- Read allocation history. Compare what this check establishes with the other devices in the path.
- Ask the owner. Compare what this check establishes with the other devices in the path.
- Review discovery limits. Compare what this check establishes with the other devices in the path.
Scope matters. IPAM allocation status is reserved. Discovery records show only observed activity, not business ownership.
Reveal the diagnosis, common mistakes and next action
What the evidence supports
The subnet is deliberately reserved for powered-off recovery systems. Owner confirmation explains the silence and contradicts automatic reclamation.
Common mistakes to avoid in this scenario
- Subnet is free: Reassign it immediately.
- Monitoring outage: Reboot all discovery services.
A proportionate next action
Retain the reservation and its evidence. Use inactivity as a review trigger, not as authorisation to delete.
Limits of the conclusion
In other cases inactivity may indicate a stale allocation. Ownership, dependencies and release approval decide what happens next.
Review the relevant platform documentation for the version and configuration in your environment.