[grade=B urn:ump:wokpmecjfauc7jvnxyyyu4fq3zkkvwge455a5mxlmi3pdzkfdw3a] feat(DC-171): DNS provider plug-in parity phase 1 — BIND 9 AXFR listing + capability honesty

RFC2136/BIND9 adapter gains listRecords via AXFR zone transfer (dig with
the same TSIG identity as nsupdate; temp 0600 keyfile, always cleaned up;
transfer-denial errors carry the exact allow-transfer fix). TSIG fields
validated (name charset, HMAC algorithm whitelist, base64 secret) before
keyfile interpolation.

Capability honesty at every surface: GET /dns/records 501s name the active
provider + its supported capabilities + zone-transfer pointer; MCP
dashcaddy_list_dns attaches actionable guidance for AI clients; setup
wizard shows per-provider capability hints at choice time (parity-pinned
by tests against the adapters).

Also fixed a latent rfc2136 bug: this._log instance property shadowed the
prototype logging method — every nsupdate call threw since the DC-170-era
refactor. CHANGELOG stale 'protocol-impossible' DC-171 entry superseded.

Judge: grade B, zero blockers (urn:ump:wokpmecjfauc7jvnxyyyu4fq3zkkvwge455a5mxlmi3pdzkfdw3a).
Polish applied post-grade: stale changelog entry corrected, TSIG field
validation + 4 extra failure-path tests (exact dig argv, ENOENT install
hint, non-denial failure passthrough, hostile-field rejection),
dns-records 501 test strengthened to pin provider name + capabilities.
Suite: backend 174 suites / 3754 tests, frontend 68/68.
This commit is contained in:
Hermes committed 2026-10-29 03:21:48 -07:00
1 parent f0ce96f471
commit 1a736c89cc
10 files changed
+704 -238

No files matched your search

+20 -4
View File
@@ -8,6 +8,19 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
## [Unreleased]
### Added
- **DC-171: DNS provider plug-in parity, phase 1 (BIND 9 upgrade + capability
honesty).** RFC 2136 adapters can now LIST records: `listRecords` performs an
AXFR zone transfer via `dig` with the same TSIG identity as nsupdate (temp
0600 keyfile, cleaned up after), parses transfer output into
`{zone, count, records}`, and — when the server denies the transfer — errors
with the exact server-side fix (`allow-transfer { key <name>; };`). The
capability matrix is pinned by a parity test suite (adapters vs wizard hints
vs route guidance). `GET /api/v1/dns/records` 501s now name the active
provider, list what it CAN do, and point at AXFR/manager tools; the MCP
`dashcaddy_list_dns` tool attaches the same actionable guidance for AI
clients; the setup wizard shows per-provider capability hints at choice time.
Also fixed a latent rfc2136 bug: an instance `_log` property shadowed the
logging method, so every nsupdate call threw after the DC-170-era refactor.
- **DC-170: full-software reliability and truth sweep (2026-10-27/29).** 46 findings
from a three-agent audit, top items fixed in 7 graded batches: TOTP gate no longer
blocks API-key/JWT auth (machine credentials were dead on every TOTP install —
@@ -54,10 +67,13 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
endpoint advertises what the running build actually does (route counts,
templates, MCP tools measured at runtime), so the marketing site, docs, and
llms.txt can never disagree with the product.
- **DC-171 (ticketed, pending): DNS provider plug-in parity** — capability
reporting at provider-choice time (RFC2136 is push-only: create/resolve yes,
listing is protocol-impossible); BIND 9 near-parity via the RFC2136 adapter
plus AXFR-based listing; PowerDNS/deSEC/AdGuard Home adapters on the roadmap.
- **DC-171 (roadmap): further provider plug-in parity** — BIND 9 AXFR-based
listing shipped in phase 1 (above); remaining roadmap: PowerDNS /
deSEC / AdGuard Home adapters, richer per-provider setup validation.
~~Capability reporting at provider-choice time~~ shipped in phase 1
(wizard hints + route guidance + MCP guidance); the original "listing is
protocol-impossible" note was superseded — RFC2136 listing works via
AXFR zone transfer with the `allow-transfer` prerequisite.
### Notes
- Historical per-change review outcomes are recorded in commit messages and in