4 Commits

Include renames

Author	SHA1	Message	Date
adamandClaude Opus 5.5	384f6b3060	Give every view a TSIG key that selects it ... Each view's match-clients starts with "key jarl-view-NAME" (after "!key" for the views listed after it), so a query signed with a view's key lands in that view from any address. The secrets are derived from a random seed in Jarl's database. The delegation check signs its queries to this server's own addresses with the key of the zone's view: before, they got whichever view matched the server's address, usually internal. jarl view key / GET /views/{id}/key show a key for dig -k (tsig:write, audited). jarl-view- key names are reserved; the importer drops view keys from a configuration Jarl wrote. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-11 18:19:10 +01:00
adamandClaude Opus 5.5	bb6b4ab64d	Stream the delegation check's queries too ... Every DNS query the name server checks send is now reported from exchangeHostPort as a dig command line with a short answer (addresses, referral, DS, NXDOMAIN) and its round-trip time; the serials check's SOA queries keep their own events with the server's result. The delegation check streams with ?stream=1 like /serials, and the Name servers tab shows its queries as they happen, keeps its result and follows a running check when you come back. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 16:00:39 +00:00
adamandClaude Opus 5.5	020223d1a5	Show the Name servers check as it happens, and keep its results ... The zone's Name servers tab no longer waits for the other servers before showing: it lists each query as a dig command line with a waiting counter, fills in the answers as they arrive, then shows the result with the queries under "Queries sent". Results (serials and delegation) are kept for 10 minutes so revisiting the tab is instant; "Check again" asks anew, and a check keeps running when the tab is left. GET /zones/{zone}/serials?stream=1 streams the queries as newline-delimited JSON (nscheck.Checker.Watch); without it the endpoint is unchanged. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-09 15:49:11 +00:00
abrown38andClaude Opus 5.5	293e6ddd33	Add backups, token expiry warnings and name server checks ... - Daily database backups: jarl-backup.timer runs 'jarld backup', which writes jarl-<UTC time>.db into backup.dir, checks it before naming it, and prunes by the time in the name while always keeping the newest keep_at_least. New backup: section in jarl.yaml; the dashboard and 'jarl status' show the newest backup and warn when it is stale or failed. The Debian package enables the timer. - 'jarld restore [FILE | latest]': checks the backup, shows it next to the current database, keeps the current one aside and records the restore. 'jarld serve' holds a database lock, so a restore can't run under a live jarld and two jarlds can't share a database. - Token expiry warnings from 14 days ahead: dashboard, token lists, a daily log line, and a CLI warning via the Jarl-Token-Expires header; 'jarl token list --expiring'. - 'jarl zone serials' and the zone page's Name servers tab: compare the serial on a primary zone's secondaries (NS records, also-notify) or a secondary zone's primaries with this server's. - 'jarl zone delegation': for zones on the internet, check the parent's delegation and glue against the zone; an undelegated zone gets a note. - Server: Jarl/<version> header; CLI exit code 2 for failed checks. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-08 19:02:34 +00:00