docs: add BIND TSIG guide and align project documentation

Create bind-tsig-configuration.md for allow-update and allow-transfer
setup. Link from README and project spec; extend .gitignore for .env files.
Record implementation decisions for change C-00001-setup-project.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
Konrad Neitzel
2026-07-04 14:27:03 +02:00
co-authored by Cursor
parent 47f17445d0
commit eff7637f86
6 changed files with 198 additions and 3 deletions
+4 -2
View File
@@ -37,7 +37,7 @@ The authoritative list lives in change **00001-setup-project** ([spec.md](change
2. **Dynamic update** — add, delete, prerequisites, batch UPDATE; typed RR builders
3. **Zone transfer** — **AXFR** only; parse stream into zone data
4. **Zone data model** — `Record`, `RRSet`, `Zone`, `UpdateResult`, `TransferResult`
5. **BIND guide** — `docs/bind-tsig-configuration.md` (how to set `allow-update` + `allow-transfer` for a key)
5. **BIND guide** — [bind-tsig-configuration.md](bind-tsig-configuration.md) (`allow-update` + `allow-transfer` for a TSIG key)
Future work: [backlog.md](backlog.md) (includes **IXFR**).
@@ -58,7 +58,9 @@ Future work: [backlog.md](backlog.md) (includes **IXFR**).
## BIND configuration
Operators configure BIND so a TSIG key may **update** and **transfer** a zone (`allow-update`, `allow-transfer`). Requirements and example are in the change spec; the standalone guide will live at **`docs/bind-tsig-configuration.md`** (written during implementation).
Operators configure BIND so a TSIG key may **update** and **transfer** a zone (`allow-update`, `allow-transfer`). Step-by-step instructions, security notes, and a minimal `named.conf` example:
**[docs/bind-tsig-configuration.md](bind-tsig-configuration.md)**
## Change workflow