← Back to home
Comparison · Infra & APIs

DNSControl vs Routinator

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

DNSControl vs Routinator: at a glance

FeatureDNSControlRoutinator
SectorInfra & APIsInfra & APIs
Velocity score5.00.0
Sparks · 30d00
Top themesdns, infrastructure-as-code, devtools, release-candidaterpki, security-hardening, cve-response, network-infrastructure
Last editorial update1h ago8d 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 Routinator?

An RPKI validator that now treats its own attack surface as the product

Routinator is a mature RPKI relying-party validator shipping on a slow, deliberate cadence — a handful of releases a year, each one gated behind release candidates. The current 0.15.x line is dominated by hardening: 0.15.2 resolves four CVEs surfaced by an external X41 D-Sec audit funded by the Sovereign Tech Agency. Feature work has narrowed to operational ergonomics — RRDP timeout tuning, repository-issue log separation, and making server mode degrade gracefully instead of stalling.

Read the full Routinator trajectory →

DNSControl vs Routinator: 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.

R
Routinator
INFRA · APIS
0.0

An RPKI validator that now treats its own attack surface as the product

◆ Current state

Routinator is a mature RPKI relying-party validator shipping on a slow, deliberate cadence — a handful of releases a year, each one gated behind release candidates. The current 0.15.x line is dominated by hardening: 0.15.2 resolves four CVEs surfaced by an external X41 D-Sec audit funded by the Sovereign Tech Agency. Feature work has narrowed to operational ergonomics — RRDP timeout tuning, repository-issue log separation, and making server mode degrade gracefully instead of stalling.

◆ Where it's heading

The arc is from feature-building to operator-trust engineering. Each recent release removes a way the validator can silently stop updating or be pushed into a panic: broken local exception files now warn instead of halting, transient connection errors no longer exit, and rsync argument handling is being locked down. Third-party audits are now part of the release process rather than an event.

◆ Prediction

Expect the 0.15.x line to continue with small hardening patches rather than new capability, with any remaining audit findings landing as point releases.

Alternatives to DNSControl and Routinator

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 Routinator.

See all DNSControl alternatives → · See all Routinator alternatives →

Recent activity from DNSControl and Routinator

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

  1. 11h 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. 2mo agoRoutinatorSecurity audit closes four CVEs in 0.15.2
  8. 10mo agoRoutinator0.15.1 stops empty-dataset starts and unblocks privileged ports
  9. 10mo agoRoutinator0.15.0 reworks RRDP timeouts and separates repository-issue logs
  10. 11mo agoRoutinator0.15.0-rc1 preview of the RRDP timeout rework
  11. 1y agoRoutinator0.14.2 fixes bundled UI pointing at the wrong instance
  12. 1y agoRoutinator0.14.2-rc1 bundles Routinator UI 0.4.5

Frequently asked questions

What is the difference between DNSControl and Routinator?

They serve adjacent needs but don't currently overlap on shipped themes. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Routinator?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. DNSControl is currently shipping more aggressively (velocity 5.0 vs 0.0), 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 Routinator?

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