Define Transaction Signature (TSIG) keys used for DDNS updates and secure zone transfers.
- to allow a DHCP Server to perform secure DDNS updates to a DNS server
- to allow a DNS Server to receive secure DDNS updates from a DDNS client
- to secure zone transfers and other DNS deployment options.
Any inter-communicating DNS Servers (such as DNS servers in a primary/secondary relationship) using the TSIG Key Server Pair DNS deployment option must all be on the same software level. For example, a primary and its secondary servers must all be running DNS/DHCP Server software version 8.1.1. DNS/DHCP Servers running different software levels might result in deployment or zone transfer failures.
For more information on the TSIG Key Pair DNS deployment option, refer to Reference: DNS deployment options.
To create a TSIG key, you specify a name for the key, an algorithm, and the length of the key in bits. Address Manager can create the key value automatically, or you can manually type a Base64-encoded string for the key. Use the manual option when you need to add keys that already exist on your DNS and DHCP servers to Address Manager.
You define TSIG keys at the configuration level on the TSIG Keys page tab found on the IP Space, DNS, Devices, TFTP, and Servers main tabs. Keys defined here can be used in DNS Deployment Options set anywhere in the configuration, and in DHCP Forward and Reverse Zones. Keys intended for use with DHCP zones must be defined with the HMAC MD5 algorithm. Keys intended for use with DNS deployment options to secure DDNS updates and zone transfers may use any of the available algorithms. For more information on using TSIG keys with DNS deployment options, refer to DNS deployment options.
A compromised key can mean part (or all) of the key has been deciphered through cryptographic analysis by a malicious attacker, or a malicious attacker has gained physical access to the keys. In either case, new keys must be generated in order to preserve the security of your DNS/DHCP environment.