⌕ PACKET DETECTIVE

All investigations.

Fictional labs. Real troubleshooting skills. Read a scenario, then investigate the evidence.

CASE 001 · IPAM

The missing network

One address space. Two different stories.

CASE 002 · IPAM

The gap in the alibi

Find the gap before approving the allocation.

CASE 003 · DNS

The record that refused to exist

The record is new. The answer is old.

CASE 004 · DNS

The name with two addresses

The VPN changes more than your location.

CASE 005 · DHCP

The office with no vacancies

The server is up. The pool is full.

CASE 006 · DHCP

The relay to nowhere

The request never reaches the right desk.

CASE 007 · IPAM

The duplicate that wasn’t

Same prefix. Different routing worlds.

CASE 008 · IPAM

The suspiciously quiet subnet

Silence is not permission to delete.

CASE 009 · DNS + DHCP

The laptop with yesterday’s address

New lease. Old name. No amount of flushing helps.

CASE 010 · DHCP

The security upgrade that broke renewals

The packets arrive. The new policy says no.

CASE 011 · DNS

The container that couldn’t find anything

One name. Four failed detours before the answer.

CASE 012 · DNS + DHCP

The lease that rewrote history

The record updates correctly. Then somebody updates it again.

CASE 013 · DHCP

The intermittent DHCP lottery

Two offers. Only one belongs here.

CASE 014 · DNS

The edit that never reached DNS

BAM shows a new record, but a direct BDDS query still returns the old address.

CASE 015 · DNS

The policy inherited from upstairs

One zone refuses expected queries after an option is changed at configuration level.

CASE 016 · DNS

The updater with the wrong badge

DHCP ACK succeeds, but a DNS update to a BlueCat-managed zone is refused.

CASE 017 · DNS + DHCP

The fixed address with no name

A fixed-address client receives its expected lease, but no DNS record appears.

CASE 018 · IPAM

The duplicate in another network view

An export flags the same prefix twice and proposes deleting one allocation.

CASE 019 · DNS + DHCP

The update at the wrong front door

NIOS DHCP allocates successfully, but the expected authoritative DNS record remains unchanged.

CASE 020 · DNS + DHCP

The lease with no permission slip

A Windows client moves scopes and gets a new lease, but authoritative DNS still contains the previous address.

CASE 021 · DHCP

The reservation the partner forgot

A client gets its reserved address from DHCP-A but a different address when DHCP-B responds.

CASE 022 · DNS

The immortal DNS record

A retired device’s dynamic DNS record survives several expected cleanup runs.

CASE 023 · IPAM

The pipeline that retried yesterday

One timeout. Two allocations. A very confident green tick.

CASE 024 · DNS

The route that outlived its resolver

One office gets DNS timeouts while another resolves normally through the same Anycast address. Both sites still advertise it. The routers would like to be excluded from the incident.

CASE 025 · DNS

The adjacency with no route

A secondary DNS server answers locally but is unreachable from a remote site. OSPF neighbours are FULL. The routing dashboard has mistaken friendship for delivery.

CASE 026 · DNS

The domain controller nobody could find

After a DNS migration, web browsing and server A-record lookups work, but new domain logons fail. Someone has declared DNS innocent on the strength of one ping.

CASE 027 · DNS

The backup with a missing key

A restored DNS server answers reads in DR, but DHCP registrations fail. The backup report says success. It did successfully back up everything included in the job.

CASE 028 · DNS

The green dashboard with the wrong answer

DNS monitoring reports 100% availability while clients connect to an old application endpoint. Every monitored query received an answer. It just was not the right answer.

CASE 029 · DNS

The two masters of one record

During platform coexistence, app.ddiengineer.com alternates between two addresses. Both automation jobs report successful reconciliation. Neither believes in compromise.

CASE 030 · DNS

The zone transfer with no guest list

A review finds that an unapproved internal host can retrieve the full lab zone. Normal DNS resolution is unaffected, which is why nobody noticed.

CASE 031 · IPAM

The inventory that stopped at page one

A reconciliation report marks 200 networks missing. The API call returned HTTP 200, and the export contains exactly 100 objects. A remarkably tidy coincidence.

CASE 032 · IPAM

The allocation race

Two deployments both read the same free address, then both attempt to claim it. Retrying faster has made the dashboard more exciting, not more correct.

CASE 033 · DNS

The redundant pair on one plug

Both DDI appliances fail during one rack power test. The inventory says “HA pair”. The rack has expressed a different architectural opinion.

CASE 034 · DNS

The answer too large for the door

Small A-record lookups work, but a larger response fails from one office. Someone suggests shortening the hostname. The hostname declines to comment.

CASE 035 · DHCP

The IPv6 address with nowhere to go

A client gets an IPv6 address and DNS settings from DHCPv6, but cannot reach off-link services. The lease is valid. The route table is less optimistic.

Follow a topic