go53 Roadmap
go53 evolves toward a modern, secure, high-performance authoritative DNS server with first-class DNSSEC and distributed operation. The project prioritizes, in order: reliability, RFC compliance, operational simplicity, performance, distributed resilience, and new features — stability and maintainability over feature count.
This page is generated automatically from the go53 Roadmap project. Status reflects the project board; see the board for live detail.
Releases
Release 0.79
Theme: Operations · Goal: Backup & Stability
| Issue | Title | Theme | Status |
|---|---|---|---|
| #20 | Add rate limiting and abuse protection | Security | Done |
| #46 | Release 0.79: Backup, WAL and point-in-time restore | Operations | Done |
Release 0.80
Theme: Performance Foundation · Goal: Remove obvious performance bottlenecks and establish benchmarks
| Issue | Title | Theme | Status |
|---|---|---|---|
| #43 | Enhancement: Normalize DNS names at write-time and eliminate fallback scans | Performance | In Progress |
| #42 | Enhancement: Remove hot-path query logging | Performance | Done |
| #45 | Enhancement: Reduce configuration lock usage on DNS request path | Performance | — |
Release 0.81
Theme: Performance · Goal: RRset Optimization
| Issue | Title | Theme | Status |
|---|---|---|---|
| #40 | Enhancement: Cache pre-built RRsets to reduce query-time allocations | Performance | — |
Release 0.82
Theme: Performance · Goal: Large Scale Zone Hosting
| Issue | Title | Theme | Status |
|---|---|---|---|
| #41 | Enhancement: Optimize authoritative zone lookup | Performance | — |
Release 0.83
Theme: DNSSEC · Goal: DNSSEC Production Hardening
| Issue | Title | Theme | Status |
|---|---|---|---|
| #22 | Verifera validate resolver interoperabilitet | DNSSEC | — |
| #26 | Improve documentation for core DNS and replication logic | Documentation | — |
| #27 | Implement RSA DNSSEC private-key import for external signer migration | DNSSEC | — |
| #44 | Enhancement: Add DNSSEC signing and cache metrics | DNSSEC | — |
Release 0.84
Theme: Distributed · Goal: Distributed Hardening
No tickets assigned yet.
Release 0.85
Theme: Operations · Goal: Production Operations
| Issue | Title | Theme | Status |
|---|---|---|---|
| #15 | Add Prometheus metrics export | Operations | — |
| #16 | Add structured logging with trace IDs | Operations | — |
| #17 | Support DNSTAP logging (optional) | Operations | — |
| #25 | Standardize admin API error responses as JSON | Operations | — |
| #28 | Support Offline Mode in go53ctl Using Direct BadgerDB Access (Future also postgres) | Operations | — |
Release 0.86
Theme: Interoperability · Goal: Modern DNS Ecosystem Support
| Issue | Title | Theme | Status |
|---|---|---|---|
| #37 | Add SSHFP and TLSA record types (RFC 4255 / RFC 6698 DANE) | Record Types | — |
| #38 | Add SVCB and HTTPS record types (RFC 9460) | Record Types | — |
Release 0.90
Theme: Release · Goal: Production Ready Community Edition
| Issue | Title | Theme | Status |
|---|---|---|---|
| #47 | Security: Support encrypted backups and WAL archives | Operations | — |
Release 1.0
Theme: Release · Goal: Recommended For Production
No tickets assigned yet.
Future / Unscheduled
Interesting ideas that are not currently roadmap priorities.
| Issue | Title | Theme | Status |
|---|---|---|---|
| #6 | Add audit logging for query and zone changes | Security | — |
| #8 | Implement Dynamic DNS (RFC 2136) | Interoperability | — |
| #19 | Add ACME-DNS support for DNS-01 challenge | Future | — |
| #21 | Support Response Policy Zones (RPZ) | Future | — |
| #39 | Add DNS-over-HTTPS (DoH) support (RFC 8484) | Future | — |
| #49 | API: MX payload field names + PATCH/DELETE owner-name form inconsistent (docs fixed for v1; v2 to correct) | — |
Themes
| Theme | Scope |
|---|---|
| Performance | QPS, latency, memory, allocation pressure, lock contention |
| Operations | Production operations: metrics, backup/restore, offline tooling, health |
| DNSSEC | Signing, validation interoperability, key rollover/management, metrics |
| Distributed | Replication, vector clocks, Merkle trees, cluster & split-brain handling |
| Interoperability | Compatibility with external DNS software, RFCs, industry standards |
| Record Types | New RR type support (TLSA, SSHFP, SVCB, HTTPS, …) |
| Documentation | Developer and operator documentation |
| Security | Security hardening and auditing |
| Future | Interesting ideas not currently prioritized |
How this roadmap works
- Priority —
P0 Critical(must ship before the next release),P1 High(on the current roadmap; 10–15 in Ready/In Progress at most),P2 Medium(valid, not yet scheduled),P3 Low(nice-to-have). - Sprints — two weeks, targeting one major item plus a few small ones; finishing work is favored over starting many in parallel.
- Future items remain open but are intentionally not assigned to a release.
The roadmap is successful when query latency drops, QPS rises, DNSSEC stays correct, distributed clusters stay stable, operators can monitor and recover easily, and external users adopt go53 in production.