← Back to home
Comparison · Infra & APIs

DNSControl vs Vault

A side-by-side editorial comparison of DNSControl and Vault — release velocity, themes, recent moves, and the top alternatives to consider.

DNSControl vs Vault: at a glance

FeatureDNSControlVault
SectorInfra & APIsInfra & APIs, DevOps
Velocity score5.02.5
Sparks · 30d00
Top themesdns, infrastructure-as-code, devtools, release-candidatevault, release-engineering, fips-140-3, hsm
Last editorial update3h ago3mo ago
WebsiteVisit →Visit →

What is DNSControl?

DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup

DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.

Read the full DNSControl trajectory →

What is Vault?

Vault under IBM lands 2.0.0, with FIPS 140-3 and HSM enterprise builds inside two weeks.

Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.

Read the full Vault trajectory →

DNSControl vs Vault: editorial side-by-side

D
DNSControl
INFRA · APIS
5.0

DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup

◆ Current state

DNSControl has locked v5.0.0 to bugfixes only with a stated ship date of 25 August 2026. rc9 carries no new capability: punycode decoding before IDNA validation in ALIDNS, a SVCB fix in POWERDNS, NAPTR and trailing-dot fixes in DYNU, a dnssort edge case, and internal refactors replacing pkg/diff and standardising on models.Records. The release notes read as a call for provider testing more than an announcement.

◆ Where it's heading

The v5 arc has run its course in public: rc1 laid out the dnsv2.RDATA refactor, rc3 finished converting every provider to it, rc4 completed the move to the Codeberg-hosted miekg/dns, and rc8 declared feature completeness. What is left is per-provider correctness on record types that only a handful of users exercise, which is why the maintainer is publishing a list of which providers most need testing rather than shipping.

◆ Prediction

Expect one or two more release candidates of provider fixes before the 25 August date, with the risk concentrated in providers nobody volunteers to test - the notes already flag PACKETFRAME as unmaintained and EXOSCALE as not supporting PTR.

Vault logo
Vault
INFRA · APISDEVOPS
2.5

Vault under IBM lands 2.0.0, with FIPS 140-3 and HSM enterprise builds inside two weeks.

◆ Current state

Vault crossed 2.0.0 in late March under its post-HashiCorp / IBM stewardship — the artifact pages now carry IBM's International Program License Agreement language alongside the existing MPL 2.0 / BSL terms. Enterprise variants followed within days: 2.0.0 enterprise FIPS 140-3 and HSM-flavored builds published April 1 and April 8, plus an sdk/v0.25.1 backport addressing a Go CVE. The recent shipping is release-engineering-heavy, not feature-heavy.

◆ Where it's heading

This is the cadence of a project completing a major-version rollout — community GA first, then RC and GA enterprise-flavor builds, then security-tracking SDK backports — rather than a roadmap pivot. The fact that FIPS 140-3 and HSM enterprise builds shipped in the same window as the 2.0 cycle is the signal worth holding onto: Vault's federal and regulated-industry posture is being kept intact under the new owner, and auth plugin version bumps suggest the wider ecosystem is staying in step.

◆ Prediction

Expect 2.x feature-bearing minor releases over the next few months, with FIPS 140-3 and HSM enterprise variants tracked alongside the community builds. GA bumps for the auth plugins to match the 2.x line are likely. Worth watching for more visible IBM branding or any Cloud-side packaging shifts that signal repositioning under the new owner.

Alternatives to DNSControl and Vault

Other Infra & APIs products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either DNSControl or Vault.

See all DNSControl alternatives → · See all Vault alternatives →

Recent activity from DNSControl and Vault

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 13h agoDNSControlDNSControl v5 rc9 sets a 25 August ship date, bugfixes only
  2. 6d agoDNSControlDNSControl v5 rc8 declared feature complete
  3. 16d agoDNSControlDNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
  4. 17d agoDNSControlDNSControl v5 rc3 finishes converting every provider
  5. 27d agoDNSControlDNSControl v5 rc2 continues the internal rewrite
  6. 29d agoDNSControlDNSControl v5 rc1 lays out the dnsv2.RDATA refactor
  7. 4mo agoVaultVault 2.0.0 Enterprise FIPS 140-3 build available
  8. 4mo agoVaultSDK 0.25.1 backports CVE-2026-34986 Go fix
  9. 4mo agoVaultVault 2.0.0 RC1 Enterprise HSM build
  10. 4mo agoVaultVault 2.0.0 RC1 release-artifacts PR
  11. 4mo agoVaultVault 2.0.0 Enterprise HSM + FIPS 140-3 build
  12. 4mo agoVaultVault 2.0.0 RC1 Enterprise HSM + FIPS 140-3 build

Frequently asked questions

What is the difference between DNSControl and Vault?

They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.

Is DNSControl better than Vault?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl is currently shipping more aggressively (velocity 5.0 vs 2.5), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Infra & APIs products to evaluate alongside.

What are the best alternatives to DNSControl?

Top DNSControl alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "DNSControl alternatives" section above for the current picks, or visit /alternatives/dnscontrol for the full list with editorial commentary on each.

What are the best alternatives to Vault?

Top Vault alternatives in Infra & APIs are ranked by recent ship velocity. Browse the "Vault alternatives" section above for the current picks, or visit /alternatives/vault for the full list with editorial commentary on each.