rsp2k/coredns
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity

Phase 0 scaffolding: RFC 2136 plugin groundwork (inactive)

Browse source 
Lays the groundwork for a future CoreDNS rfc2136 plugin that will accept
TSIG-authenticated dynamic DNS updates from Caddy (via caddy-dns/rfc2136),
enabling self-hosted ACME DNS-01 cert automation without depending on
registrar APIs.

Nothing in this commit is active at runtime:
- Corefile additions are commented out
- coredns/Dockerfile references a plugin repo that doesn't exist yet
- scripts/acme-add-domain.sh just appends CNAME glue but has nothing
  to talk to until the plugin is built

Architecture and implementation plan:
  ~/.claude/plans/dood-does-coredns-offer-enumerated-piglet.md

Secret management: TSIG key generated and stored in .env.local
(gitignored). .env.local.example documents the expected shape.
This commit is contained in:
Ryan Malloy 2026-05-20 18:20:43 -06:00
parent 9e345fa488
commit 48cddc91cf
4 changed files with 140 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

7
.env.local.example Normal file
View file

@ -0,0 +1,7 @@
# Template for .env.local — copy to .env.local and fill in real values.
# .env.local is gitignored; this file documents what must be in it.
# TSIG shared secret for rfc2136 plugin + caddy-dns/rfc2136.
# Generate with: openssl rand -base64 32
# Rotate by regenerating + restarting CoreDNS + Caddy.
ACME_TSIG_SECRET=