DNSControl
Infrastructure-as-code system for managing DNS zones across many providers
DNSControl v5 is feature-frozen with a ship date, and rc9 is pure provider cleanup
◆Recent moves
- 28d ago
DNSControl v5 rc9 sets a 25 August ship date, bugfixes only
Bugfixes only, as the feature freeze requires: provider-specific record handling for ALIDNS, POWERDNS, DYNU and others, plus refactors with no user-visible effect. The ship date of 25 August is the actual news here, not the changelog.
View source ↗ - 1mo ago
DNSControl v5 rc8 declared feature complete
The candidate that declared v5 feature complete, closing the window on the refactor that has defined this line since rc1.
View source ↗ - 1mo ago
DNSControl v5 rc4 completes the move to Codeberg-hosted miekg/dns
Completes the move to the Codeberg-hosted miekg/dns. A dependency relocation rather than a feature, but one that determines where the project's core DNS library lives for the next several years.
View source ↗ - 1mo ago
DNSControl v5 rc3 finishes converting every provider
Every provider finishes converting to the new record model. The largest single step in the v5 refactor, and the point after which the remaining work became testing rather than porting.
View source ↗ - 1mo ago
DNSControl v5 rc2 continues the internal rewrite
An incremental candidate continuing the internal rewrite with nothing surfacing for users.
View source ↗ - 1mo ago
DNSControl v5 rc1 lays out the dnsv2.RDATA refactor
Lays out the dnsv2.RDATA refactor that the whole v5 line implements. Reading the arc backwards, this is where the shape of the release was decided.
View source ↗