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

DNS disaster recovery: missing TSIG transfer 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.

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: Synthetic RFC 2136/TSIG integration. Configuration restore deliberately excludes separately managed TSIG material. No vendor encryption-format claim is implied.

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 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.

Checks to compare

  1. Inspect transaction and identity. Compare what this check establishes with the other devices in the path.
  2. Compare recovery inventory. Compare what this check establishes with the other devices in the path.
  3. Exercise complete recovery. Compare what this check establishes with the other devices in the path.

Scope matters. Synthetic RFC 2136/TSIG integration. Configuration restore deliberately excludes separately managed TSIG material. No vendor encryption-format claim is implied.

Reveal the diagnosis, common mistakes and next action

What the evidence supports

Read-only DNS success did not validate the DDNS dependency. The restore manifest and explicit authentication failure locate the missing recovery component.

Common mistakes to avoid in this scenario

  • Transfer authentication is unnecessary during recovery: Allow unsigned transfers broadly to make the drill pass.
  • The restored zone contains the wrong data: Reload the zone; leave transfer authentication unchanged.

A proportionate next action

Recover the authorised key securely, verify policy and complete write-path tests; update the DR inventory and runbook.

Limits of the conclusion

Never place secret values in a case, log or dashboard. Restoring arbitrary production keys into a test environment requires authorisation.

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