DDIENGINEER.COM / FICTIONAL NETWORKS. REAL TROUBLESHOOTING.NO PRODUCTION SYSTEMS WERE REBOOTED.
⌕ PACKET DETECTIVE
DNS + SECURITY / ADVANCED

DNS security: unrestricted zone transfers

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

What you’ll practise

Trace the supplied evidence, challenge alternative explanations, and choose a safe next action. Use the topology and private notebook to document your reasoning.

Lab scope: Authorised security-review exercise against a synthetic zone only. Policy permits transfers to two named secondary endpoints; no open-transfer requirement exists.

Validation: Original synthetic operational lab; not a reproduced vendor defect

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 review finds that an unapproved internal host can retrieve the full lab zone. Normal DNS resolution is unaffected, which is why nobody noticed.

Checks to compare

  1. Check transfer policy and effective ACL. Compare what this check establishes with the other devices in the path.
  2. Verify response and scope. Compare what this check establishes with the other devices in the path.
  3. Validate least-privilege correction. Compare what this check establishes with the other devices in the path.

Scope matters. Authorised security-review exercise against a synthetic zone only. Policy permits transfers to two named secondary endpoints; no open-transfer requirement exists.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

The effective ACL and controlled transfer demonstrate unauthorised data access under the organisation’s stated policy.

Common mistakes to avoid in this scenario

  • Transfer authentication already covers every source: Keep the broad transfer ACL because approved secondaries use signed transfers.
  • Recursion is the only exposure: Disable recursion and assume authoritative zone transfers are now restricted.

A proportionate next action

Narrow transfer permissions and validate secondary continuity without blocking legitimate client queries.

Limits of the conclusion

This is a security-policy finding, not automatically a specific regulatory violation. Determine applicable obligations with the relevant owners.

Read the technical reference →

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