DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
IPAM · Foundation

Reconcile overlapping IPAM prefixes across VRFs

The duplicate that wasn’t. A global duplicate detector flags 10.80.0.0/24 twice. An automated cleanup proposal recommends deleting one record. It has not asked the tenants for their opinion.

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: Two isolated VRFs with no route leaking. Reuse is approved by the lab policy. This is not a shared routing 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.

DDIENGINEER.COM / INTERACTIVE NETWORK INVESTIGATIONS

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.

ADVANCED · DNS + DHCP · ~8 MIN

Realistic DNS, DHCP and IPAM mysteries.
No lab setup. No production access. Just your judgement.

01 Inspect the clues02 Build your theory03 Make the call
FEATURED / PD–009DNS + DHCP
THE LAPTOP WITH YESTERDAY’S ADDRESS

New lease.
Old address.
Same confused user.

09:30 / DHCP ACK10.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.

FIELD NOTES / READ BEFORE OR AFTER THE LAB

Troubleshooting guide

Recognise the symptoms

A global duplicate detector flags 10.80.0.0/24 twice. An automated cleanup proposal recommends deleting one record. It has not asked the tenants for their opinion.

Checks to compare

  1. Inspect ownership metadata. Compare what this check establishes with the other devices in the path.
  2. Inspect routing isolation. Compare what this check establishes with the other devices in the path.
  3. Test a scoped reconciliation key. Compare what this check establishes with the other devices in the path.

Scope matters. Two isolated VRFs with no route leaking. Reuse is approved by the lab policy. This is not a shared routing domain.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

The CIDRs are identical but belong to separate, deliberately isolated routing domains. CIDR-only uniqueness creates a false positive.

Common mistakes to avoid in this scenario

  • Remove the duplicate: Delete tenant B’s allocation.
  • Combine the records: Treat both tenants as a single network.

A proportionate next action

Use the platform’s actual routing/tenant identity model when detecting conflicts. Check policy and interconnection before accepting overlap.

Limits of the conclusion

VRF labels alone do not guarantee safe reuse. Here the evidence includes isolation and an explicit allocation policy.

Review the relevant platform documentation for the version and configuration in your environment.

Browse all investigations →

Browse troubleshooting case guides →The missing networkThe gap in the alibiThe record that refused to existThe name with two addressesThe office with no vacanciesThe relay to nowhereThe duplicate that wasn’tThe suspiciously quiet subnetThe laptop with yesterday’s addressThe security upgrade that broke renewalsThe container that couldn’t find anythingThe lease that rewrote historyThe intermittent DHCP lotteryThe edit that never reached DNSThe policy inherited from upstairsThe updater with the wrong badgeThe fixed address with no nameThe duplicate in another network viewThe update at the wrong front doorThe lease with no permission slipThe reservation the partner forgotThe immortal DNS recordThe pipeline that retried yesterdayThe route that outlived its resolverThe adjacency with no routeThe domain controller nobody could findThe backup with a missing keyThe green dashboard with the wrong answerThe two masters of one recordThe zone transfer with no guest listThe inventory that stopped at page oneThe allocation raceThe redundant pair on one plugThe answer too large for the doorThe IPv6 address with nowhere to go