- DigiCert product docs
- DigiCert DNS
- Release notes
Release notes
Notice
For maintenance schedules and older releases, visit the What's new section of this website.
Recent releases
November 18, 2026
DigiCert® DNS version: 2.0.0
New
Primary and secondary DNS management
Manage DNS records directly in primary zones or use DigiCert® DNS as a secondary provider that receives updates from your existing primary provider. Configure zone transfers and notifications to keep DNS data synchronized across providers.
Populate new primary zones by importing records, copying records from an existing zone, or requesting an AXFR transfer. Convert a secondary zone to primary while retaining its transferred records, or request a transfer to refresh a secondary zone. Review assigned nameservers and delegation status to verify your setup.
DNS record management and migration
Create and manage DNS records for website and application routing, email delivery and authentication, service discovery, certificate authorization, and reverse DNS.
Supported record types include A, AAAA, ALIAS, CAA, CERT, CNAME, DS, HINFO, HTTPS, MX, NAPTR, NS, PTR, RP, SRV, SSHFP, SVCB, TLSA, and TXT. TXT record options include Generic, SPF, DKIM, DMARC, and BIMI. Optional PTR record creation when adding A and AAAA records helps configure reverse DNS.
Import records from zone files or BIND text. The API also supports record-set replacement and partial updates, imports that add or replace records, and exports of up to 250 zones as BIND zone files packaged in a ZIP archive.
Regional DNS responses
Customize DNS responses for different geographic regions within a single zone. Apply regional overrides to supported record types, using the global configuration as the default where no override exists. Configure regional exclusions to suppress responses for a particular record name and type, including the global fallback.
Through the API, retrieve the effective records for a region, inspect its overrides, and list the regions configured for a zone or record set.
Health-based DNS failover
Configure prioritized destinations for A and AAAA records to help maintain service availability. Simple failover uses endpoint health and priority to select a destination, with controls to enable or disable individual endpoints and inspect their health and serving state.
Supported monitoring protocols include HTTP, HTTPS, TCP, UDP, and ICMP. If all enabled endpoints are unhealthy, the service uses the highest-priority enabled endpoint as a last resort.
DNSSEC signing
Sign primary zones with DNSSEC so validating resolvers can verify the authenticity and integrity of DNS responses. View signing keys, manage key rollover, and obtain the DS records needed to complete the chain of trust through your domain registrar.
The API supports zone signing, signing-status and key retrieval, and a separate DNSSEC health check that compares expected DS records with those published in the parent zone.
Zone snapshots and recovery
Save snapshots of eligible primary zones before making changes and restore a saved state when needed. Snapshots can preserve regional views alongside zone records and configuration, and can be downloaded in JSON format.
Through the API, create and list snapshots, retrieve their captured record sets, restore saved records, and delete snapshots that are no longer needed. Snapshot creation and restoration run asynchronously so integrations can track completion.
Shared DNS configurations
Reuse nameserver sets, SOA configurations, and zone-transfer settings across zones. Configure inbound and outbound IP sets to control transfer sources and destinations, and use TSIG keys to authenticate transfers and notifications.
The API provides management operations for nameserver sets, IP sets, and TSIG keys, along with access to account-default SOA settings.
Team access and API credentials
Assign built-in roles to control access to DNS resources and account administration. Create dedicated service users for applications and automated processes, and manage API tokens that use their associated identity’s permissions.
Through the API, manage existing users’ account access, create service users, assign roles, and inspect effective permissions. Generate tokens with optional expiry dates, enable or revoke credentials, and permanently delete tokens that are no longer needed.
DNS monitoring and operational visibility
Review nameserver delegation, SOA serial-number consistency, and zone-transfer activity from each zone’s Health page. Track configuration changes in audit logs and review operation results in Tasks. Administrators can configure alerts for selected account events, DNS changes, and usage thresholds.
The API provides zone-health results, recent transfer details, searchable audit records, and audit exports in JSON or CSV.
Usage reporting and query analytics
Track account usage against subscription allowances, with monthly, daily, and per-zone breakdowns. Explore query activity by name, record type, response code, data center, and other attributes to investigate traffic patterns and operational issues.
Use the API to retrieve usage summaries and account entitlements, and generate monthly per-zone query-volume reports for reporting and capacity planning.
CertCentral integration
Connect DigiCert® DNS with DigiCert CertCentral® to support automated DNS-based domain control validation. Link the integration at the account level, then enable it for selected primary zones.
The API supports linking, status retrieval, replacement activation credentials, and unlinking. Complete activation by configuring the generated credentials in DigiCert CertCentral®.
Valimail Monitor integration
Enable Valimail Monitor to identify services sending email on behalf of your organization and monitor DMARC compliance. Configure the integration for your account, then enable monitoring for selected primary zones.
The integration supports global and regional DMARC TXT records, preserving existing policies while adding the required Valimail reporting address. Regional exclusions are preserved. Regional overrides can use different DMARC policies while retaining the required reporting address.
Generally available DNS APIs
Automate DNS provisioning, configuration, monitoring, recovery, and account access through two generally available REST APIs: Zone and record management and Users and access.
Both APIs use https://api.dns.digicert.com/v1 and authenticate requests through the X-API-Key header. OpenAPI definitions are available for compatible development tools.
Batch operations and asynchronous tasks
Group supported API operations to manage resources at scale. Synchronous write batches support up to 50 operations, and asynchronous batches support up to 1,000. Batch-read requests let you retrieve multiple resources together.
Track asynchronous task status, progress, results, and available resource links to confirm completion before starting dependent operations.
Known issues
Batch operation limitations
If a write-batch sub-request fails, later sub-requests are not run and earlier changes are not retained. The onFailure parameter has no effect in this release. Zone actions such as :transfer cannot be batched.
Incomplete DNS health information through the API
AXFR host and NOTIFY activity information is not available through the APIs in this release. DNSSEC health is retrieved separately and does not contribute to the overall zone-health result.
Missing resource location headers
Some 201 Created API responses omit the Location header when creating an immediately available zone, inbound IP set, TSIG key, or integration link. Use the resource ID or name returned in the response body instead.
Snapshot eligibility restrictions
API snapshot creation requires a primary zone that is not DNSSEC-signed or suspended and contains no more than 50,000 records.
Task management limitations
Pending or running tasks cannot be cancelled. Only completed tasks can be deleted through the API, and deletion requires the Account admin role. Filtering the task list by status is not supported in this release.
User administration boundaries
The Users and access API manages existing users’ account access and roles. It does not create user identities or update personal profile details. Protected service users also restrict configuration, role, and token changes.
Zone exports can omit requested zones
API zone exports skip zones that do not exist or that the authenticated identity cannot read, without failing the export task. Compare the archive contents with the requested zones to identify omissions.
Zone status restrictions
The API supports ACTIVE, DISABLED, and SUSPENDED status updates for primary zones. Secondary zones support only ACTIVE and SUSPENDED.