Manual Chapter :
Generating External HSM Key-Cert Pairs for DNSSEC
Applies To:
Show VersionsBIG-IP AAM
- 14.0.1, 14.0.0
BIG-IP APM
- 14.0.1, 14.0.0
BIG-IP LTM
- 14.0.1, 14.0.0
BIG-IP AFM
- 14.0.1, 14.0.0
BIG-IP DNS
- 14.0.1, 14.0.0
BIG-IP ASM
- 14.0.1, 14.0.0
Generating External HSM Key-Cert Pairs for DNSSEC
Overview: Generating external HSM key and certificate pairs for manually managed DNSSEC keys
When the BIG-IP® system is a BIG-IP DNS (previously Global Traffic Manager), you can use the Thales nShield Connect to store and manage DNSSEC keys.
For additional information about using Thales nShield Connect, refer to the Thales website: (https://www.thales-esecurity.com).
Task list
Generating an external key for creating manually managed DNSSEC keys
Before you generate the key, make sure that the Thales nShield Connect client is
running on all BIG-IP
DNS devices in the configuration synchronization group.
You can use the Traffic Management
Shell (tmsh) to
generate a key and certificate.
When you generate a key/certificate
using tmsh, the system
creates a HSM private key. It also creates a local key, which points to the HSM key,
residing in the HSM.
Creating a DNSSEC key using an external HSM key and certificate
Before you create a DNSSEC key using an external key and certificate,
make sure that you have generated a key and certificate using Thales nShield
Connect, and that you have loaded the key and certificate.
You can create manually managed DNSSEC zone-signing and key-signing keys
for use with an external HSM. For more information, see Configuring
DNSSEC with an external HSM in BIG-IP DNS
Services: Implementations at http://support.f5.com.