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
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
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
- Inspect transaction and identity. Compare what this check establishes with the other devices in the path.
- Compare recovery inventory. Compare what this check establishes with the other devices in the path.
- 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.