TSIG keys
TSIG keys authenticate DNS messages used for zone transfers and notifications. In DigiCert® DNS, you can create and manage keys for use with your inbound and outbound zone transfer configurations.
What a TSIG key is
A Transaction Signature (TSIG) key uses a shared secret and an authentication algorithm to verify DNS messages exchanged between servers. TSIG provides message authentication and integrity checking; it does not encrypt the transferred zone data.
A TSIG key configuration contains three components:
Component | Purpose |
|---|---|
Name | Identifies the key |
Algorithm | Specifies the algorithm used to authenticate DNS messages |
Shared secret | Provides the secret value used by both parties to generate and verify message authentication codes |
The participating DNS servers must agree on the TSIG key identity, algorithm, and shared secret for authentication to succeed.
Explore the TSIG keys page
To view TSIG keys in your account, go to Configuration > Product settings and select the TSIG keys tab.
The page displays the following information:
Column | Description |
|---|---|
Name | The name of the TSIG key |
Algorithm | The authentication algorithm configured for the key |
Shared secret | A masked version of the shared secret |
Zones | The number of zones using the key. Select the count to view the applied zones |
To view the zones using a key, select its count in the Zones column. The Applied zones panel lists those zones. Select a zone name to open it.
Create a TSIG key
Select Create TSIG key.
Enter a Name that identifies the key.
Select an Algorithm compatible with the other DNS provider. HMAC-SHA256 is recommended for new keys.
Enter a Shared secret, or select Auto-generate shared secret.
Securely retain the secret for configuration at the other DNS provider.
Select Create.
After creating the key, select it in the relevant zone transfer configuration and configure the corresponding key details at the other DNS provider.
To edit a key, select its edit icon, update the required fields, and select Update. If a confirmation appears, review the impact before confirming.
To delete a key, select its delete icon when available and confirm the deletion. Deletion cannot be undone.
The impact of changing a TSIG key
Changing a key’s authentication details can affect zone transfers and notifications that depend on it.
When you update a shared secret, DigiCert® DNS warns that the change may affect inbound and outbound IP sets using the key. If the participating servers use different secrets or algorithms, authentication can fail.
Before changing a key:
Review its applied zones using the Zones count.
Identify the inbound and outbound configurations that use it.
Coordinate the change with the relevant DNS providers.
Prepare the corresponding configuration changes on both sides.
Update a TSIG key
Go to Configuration > Product settings and select the TSIG keys tab.
Select the key’s edit icon.
Update the required fields.
Select Update.
Review and confirm the update when prompted.
After updating both sides, verify that the affected zone transfers and notifications operate successfully.
If only some zones should use the new authentication details, create a separate key and change those zones’ assignments.
TSIG key algorithms
The algorithm determines how DNS messages are authenticated using the shared secret. Choose an algorithm supported by both DigiCert® DNS and the other DNS provider.
The algorithm menu provides the following options:
Algorithm | Guidance |
|---|---|
HMAC-MD5 | Legacy option retained for compatibility. Do not use for new keys |
HMAC-SHA1 | Legacy option retained for compatibility. Not recommended for new keys |
HMAC-SHA224 | Supported for interoperability with systems that require SHA-224 |
HMAC-SHA256 | Recommended for new TSIG keys |
HMAC-SHA384 | Supported for interoperability with systems that require SHA-384 |
HMAC-SHA512 | Supported for interoperability with systems that require SHA-512 |
Tip
Use HMAC-SHA256 for a new key unless the other provider requires a different supported algorithm.
Shared-secret options
You can supply a shared secret or generate one in DigiCert® DNS.
Option | When to use it |
|---|---|
Enter a shared secret | The other DNS provider has supplied a secret, or you already have one to use |
Auto-generate shared secret | You need a new secret and will configure it at the other DNS provider |
When entering an existing secret, copy the complete value accurately. When generating a secret, securely retain the value and configure the same secret at the other provider.
Treat the shared secret as a credential. Store and exchange it securely, and limit access to the people and systems that need it.
The TSIG keys page masks the secret in the table.
Use TSIG keys with inbound and outbound IP sets
Select a TSIG key when configuring authenticated zone transfers and notifications.
Configuration | Use |
|---|---|
Inbound IP set for a secondary zone | Select the key agreed with the primary DNS provider |
Outbound IP set for a primary zone | Select the key agreed with the external secondary DNS provider |
For a secondary zone, open its Settings tab and select the edit icon beside Inbound IP sets. Select the required TSIG key alongside the inbound IP set, then select Apply.
For a primary zone, open its Settings tab and select the edit icon beside Outbound IP sets. Select the required TSIG key for each outbound IP set, then select Apply.
You can also select a key during zone creation. Where available, select Create TSIG key from the key menu to create a new key.
Reuse TSIG keys across zones
A TSIG key can be used by multiple zones. For example, several zones using the same external DNS provider may use the same key.
Before editing a reused key, select its Zones count to review the affected zones. Coordinate changes with every DNS provider or server that uses the key.
If a group of zones needs different authentication details, create a separate key and assign it to those zones.