DNScale Terraform Provider 1.0.1: safer DNS-as-code updates

DNScale Terraform Provider v1.0.1 is now available for teams managing DNS with Terraform.

This release keeps the same provider source, dnscaleou/dnscale, and focuses on making day-to-day DNS-as-code workflows more predictable after the initial 1.0 release.

What changed

Zone listings now follow pagination

The dnscale_zones data source now follows DNScale API pagination automatically. If your account has more zones than a single API page returns, Terraform receives one combined zone list instead of only the first page.

This is especially useful for MSPs, agencies, and infrastructure teams that use Terraform to inventory many customer or environment zones.

Record changes handle replacement and new IDs more cleanly

DNS record identity is tied to fields such as name, type, and content. Provider v1.0.1 now treats record name and type changes as replacements, and it lets Terraform state follow the new record ID when the API returns a different ID after a content update.

The provider also handles missing remote records, zones, and DNSSEC keys more cleanly during reads and deletes. If a resource was already removed outside Terraform, state can converge instead of surfacing avoidable follow-up errors.

DNSSEC CSK support

The dnscale_dnssec_key resource now accepts CSK for combined signing keys, alongside KSK and ZSK.

resource "dnscale_dnssec_key" "csk" {
  zone_id   = dnscale_zone.example.id
  key_type  = "CSK"
  algorithm = "ECDSAP256SHA256"
  active    = true
  published = true
}

The dnscale_dnssec_status data source also accounts for CSK keys when reporting whether a zone has the signing material expected for DNSSEC.

API contract and documentation alignment

The provider docs and examples now match the published registry source, dnscaleou/dnscale, and the current DNScale API contract more closely.

The update also documents:

• dnscale_zones pagination behavior
• supported zone regions, including EU, GLOBAL, and EU_GLOBAL
• record TTL validation from 300 to 86400 seconds
• the current supported record type set
• local testing and release workflow notes for provider maintainers

Upgrade

If your Terraform configuration already allows the 1.0 series, run:

terraform init -upgrade

If you pinned the provider exactly to 1.0.0, update the constraint first:

terraform {
  required_providers {
    dnscale = {
      source  = "dnscaleou/dnscale"
      version = ">= 1.0.1, < 2.0.0"
    }
  }
}

For most configurations this should be a direct patch upgrade. Review any records with TTL values below 300 seconds and any DNSSEC key definitions that still use older lowercase or numeric examples before applying.

Links

• Terraform Registry provider
• Provider documentation
• Source code
• Managing DNS with Terraform