- DigiCert product docs
- DigiCert DNS
- API integration
- Validation messaging
- DNS resource validation messaging
DNS resource validation messaging
This document lists the validation messages for DNS resources such as domains, fields, and records. These messages help identify misconfigurations that could impact resolution, availability, or automation.
Select a section to view its specific validation and messaging.
| Validation | Messaging | 
|---|---|
|   | Domain IDs are required and cannot be empty. | 
|   |  ' | 
|   |  The domain, ' | 
|   |  A domain with the name ' | 
|   |  The domains, ' | 
|   | A maximum of 10 domains can be created at once. | 
|   |  The secondary domain, ' | 
| Validation | Messaging | 
|---|---|
|   |  The ' | 
|   |  The ' | 
|   |  A list of IDs is required in the ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The ' | 
|   |  The request path parameter type, ' | 
| Validation | Messaging | 
|---|---|
|   |  The default GTD region, ' | 
|   | GTD is not enabled for this account. | 
|   |  The domain, ' | 
|   |  The GTD region name, ' | 
|   |  ' | 
|   |  The GTD region, ' | 
|   |  The GTD region, ' | 
| Validation | Messaging | 
|---|---|
|   |  The nameserver set, ' | 
|   |  The default nameserver set of the account, ' | 
|   |  The nameserver set, ' | 
|   | Nameserver set names are required and cannot be empty. | 
|   |  Neither the name nor nameservers of the system nameserver set, ' | 
|   |  The system nameserver set, ' | 
|   |  The system nameserver set, ' | 
|   |  The system nameserver set, ' | 
|   |  The nameserver set, ' | 
|   |  The nameserver set, ' | 
|   |  The account, ' | 
|   |  The nameserver sets, ' | 
|   |  A nameserver set with the name ' | 
|   |  The domain, ' | 
| Validation | Messaging | 
|---|---|
|   | Either a nameserver ID or FQDN must be provided. | 
|   |  Nameserver sets must contain  | 
|   |  The nameserver, ' | 
| Validation | Messaging | 
|---|---|
|   |  The maximum number of combined records for this endpoint is  | 
|   |  A/an ' | 
|   | Duplicate records are not allowed. | 
|   | Record names are required and cannot be empty. | 
|   |  Record names cannot contain ' | 
|   |  Record names cannot contain special characters. Only ' | 
|   |  Record names cannot end with ' | 
|   |  The record's name cannot be ' | 
|   |  Record names can neither start nor end with ' | 
|   |  Record names cannot start with ' | 
|   |  The record, ' | 
|   |  The record, ' | 
|   |  ' | 
|   | System records cannot be deleted. | 
|   |  The system record, ' | 
|   |  Setting ' | 
| Validation | Messaging | 
|---|---|
|   |  The value, ' | 
| Validation | Messaging | 
|---|---|
|   | This configuration blocks all CAs from issuing any certificates. Reporting via IODEF remains enabled. | 
|   | The IODEF tag in CAA records must use a custom Provider value. | 
|   | The 'issuerCritical' field must contain a value of 0 or 1. | 
|   | This configuration blocks wildcard certificate issuance by CAs but allows standard certificate issuance. Reporting via IODEF remains enabled. | 
|   | CAA records with multiple values cannot be used without a specified provider. | 
|   | A value is required when no provider is specified for a CAA record. | 
|   | This configuration blocks certificate issuance by CAs but allows wildcard certificates. Reporting via IODEF remains enabled. | 
|   |  The specified provider, ' | 
|   |  ' | 
|   |  ' | 
|   |  ' | 
|   |  ' | 
|   |  ' | 
|   |  ' | 
|   | The value, ';', is only valid when 'No Provider' is selected. | 
|   |  ' | 
|   | A maximum of 10 CAA values is allowed per record. | 
| Validation | Messaging | 
|---|---|
|   |  The CNAME alias, ' | 
|   |  The CNAME alias, ' | 
|   |  The CNAME alias, ' | 
|   |  The CNAME alias, ' | 
|   |  ' | 
|   |  The CNAME record, ' | 
|   |  As per RFC standard 1034, CNAME loops are not allowed. The record name ' | 
|   |  As per RFC-2181, ' | 
| Validation | Messaging | 
|---|---|
|   | A maximum of 15 MX values is allowed per record. | 
|   | Multiple MX values are not allowed when using a 'No service' value of '.'. | 
|   | The value's priority must be 0 when specifying a 'No service' value of '.'. | 
|   | MX server values are required. | 
| Validation | Messaging | 
|---|---|
|   | A maximum of 10 NS values is allowed per record. | 
|   | Duplicate hostnames are not allowed. | 
|   | The root NS record must be placed in the default GTD region. | 
| Validation | Messaging | 
|---|---|
|   | A maximum of 10 PTR values is allowed per record. | 
| Validation | Messaging | 
|---|---|
|   |  The default SOA record name, ' | 
|   |  The SOA record, ' | 
|   |  The default SOA record, ' | 
|   |  The default SOA record of the account, ' | 
|   |  The SOA record ID, ' | 
|   |  The SOA record, ' | 
|   |  The SOA record, ' | 
|   |  ' | 
|   | The field, 'startingSerial', cannot be updated. | 
|   |  The SOA records, ' | 
| Validation | Messaging | 
|---|---|
|   | A maximum of 15 SRV values is allowed per record. | 
|   |  The SRV value, ' | 
|   | SRV values are required. | 
| Validation | Messaging | 
|---|---|
|   |  ' | 
|   | A maximum of 15 TXT values is allowed per record. | 
|   |  The TXT record, ' | 
|   |  The TXT value, ' | 
| Validation | Messaging | 
|---|---|
|   |  ' | 
|   |  The TSIG key, ' |