DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS - 9104 (0x2390)

The zone does not have enough signing keys. There must be at least one key signing key (KSK) and at least one zone signing key (ZSK).

Updated: Feb 21, 2026

Technical Background

The DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS error indicates that a DNS zone is missing the required number of signing keys. This error is specific to the Windows DNS Server service and is related to cryptographic operations necessary for secure zone management.

Error Details

This error code, 9104 (0x2390), signifies that the zone configuration does not meet the minimum requirements for key management. Specifically, there must be at least one Key Signing Key (KSK) and one Zone Signing Key (ZSK). The absence of these keys can lead to security vulnerabilities and operational issues.

Common Causes

  • Invalid parameter values: Incorrect or missing parameters during zone configuration.
  • Incorrect object type: Misconfiguration of the DNS zone, leading to insufficient key descriptors.
  • Exceeding limits: Attempting to configure a zone with too many or too few keys, violating predefined constraints.
  • Corrupted data: Data corruption in the DNS zone file or database.
  • Unsupported operations: Performing actions that are not supported by the current configuration of the DNS server.

Real-World Context

This error typically occurs during the setup or maintenance of a secure DNS zone. It is crucial for administrators to ensure that the necessary keys are properly configured and available to maintain the security and integrity of the DNS zone.

Is This Error Critical?

The DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS error is critical as it directly impacts the security and functionality of a DNS zone. Without proper key management, the zone may become vulnerable to tampering or unauthorized access.

How to Diagnose

To diagnose this issue, follow these steps:

  1. Review operation context: Ensure that the zone configuration aligns with best practices for secure DNS management.
  2. Validate parameters: Check all input parameters used during zone setup and maintenance.
  3. Confirm object types: Verify that the correct key types (KSK and ZSK) are present in the zone.
  4. Verify input data: Ensure that the keys are correctly generated and imported into the DNS server.
  5. Check limits or constraints: Confirm that the number of keys does not exceed any predefined limits.

How to Resolve

To resolve this issue, take the following actions:

  1. Correct parameter usage: Ensure all parameters used in zone configuration are valid and correct.
  2. Adjust operation context: Modify the zone configuration as necessary to meet the required key descriptors.
  3. Restore data: If keys have been corrupted or lost, regenerate them according to best practices.
  4. Retry operation with valid inputs: Attempt the operation again using validated and properly configured parameters.

Developer Notes

Developers should ensure that their applications are designed to handle secure DNS configurations and provide appropriate error messages when encountering issues such as DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS. This helps in diagnosing and resolving problems more effectively.

Related Errors

  • DNS_ERROR_NO_KX_RECORD: Indicates the absence of a KSK record.
  • DNS_ERROR_NO_ZSK_RECORD: Indicates the absence of a ZSK record.
  • DNS_ERROR_ZONE_HAS_NO_KEY: Indicates that the zone does not have any keys configured.

FAQ

Q: What is the difference between a Key Signing Key (KSK) and a Zone Signing Key (ZSK)?

A: A KSK is used for signing other keys, while a ZSK is used to sign DNS resource records. Both are essential for secure zone management.

Q: Can this error occur in non-DNS environments?

A: No, this specific error code is related to the Windows DNS Server service and does not apply to other environments or services.

Summary

The DNS_ERROR_NOT_ENOUGH_SIGNING_KEY_DESCRIPTORS error indicates a critical issue with the configuration of a secure DNS zone. Ensuring that both KSK and ZSK keys are properly configured is essential for maintaining the security and integrity of the DNS zone.