TSIG (Transaction Signature)
What is TSIG (Transaction Signature)?
TSIG, defined in RFC 8945, authenticates a DNS message using a secret key shared between two servers, rather than trusting the message based on where it came from, by attaching a keyed hash over its contents plus a timestamp. It's the cryptographic alternative to IP-based allow-listing for zone transfers, which AdminKit's AXFR guide covers from the other side.
By AdminKit team, Netbase JSC · Updated
TSIG (Transaction Signature) is a mechanism, defined in RFC 8945, for authenticating a DNS message using a secret key shared between two servers, rather than trusting the message based on where it came from. Each signed message carries a keyed-hash (HMAC) computed over its contents plus a timestamp, so the receiving server can confirm both that the sender holds the shared secret and that the message hasn’t been replayed or altered in transit.
It is most commonly used to control zone transfers (AXFR) and DNS UPDATE (dynamic DNS updates): instead of, or alongside, restricting those operations to an allow-list of IP addresses, a server can require a valid TSIG signature, which still works correctly even if the requesting server’s IP address changes — NIST’s DNS deployment guide recommends exactly this, authenticating zone transfers and dynamic updates with TSIG rather than relying on IP address alone. Because the secret is shared out of band and never sent in the DNS message itself, TSIG is vulnerable only if that secret leaks, not to IP spoofing. In BIND, for example, the TSIG section of the Administrator Reference Manual generates such a key with tsig-keygen (HMAC-SHA256 by default) and lets it be named in allow-transfer and allow-update access lists. The specific HMAC algorithms a TSIG implementation may use — and which ones RFC 8945 marks mandatory versus optional to support — are tracked in IANA’s TSIG Algorithm Names registry, separate from the RFC itself so a new algorithm can be added without revising the base specification.
AdminKit groups tSIG (Transaction Signature) under its DNS cluster — browse the AdminKit glossary index for other related terms.
Frequently asked questions
What does TSIG authenticate?
A DNS message, using a secret key shared between two servers, rather than trusting the message based on where it came from.
What is TSIG most commonly used for?
Controlling zone transfers (AXFR) and DNS UPDATE (dynamic DNS updates).
What advantage does TSIG have over IP-based allow-listing?
It still works correctly if the requesting server's IP address changes, and is vulnerable only if the shared secret leaks, not to IP spoofing.
Where are TSIG's allowed HMAC algorithms tracked?
IANA's TSIG Algorithm Names registry, kept separate from RFC 8945 so a new algorithm can be added without revising the base specification.