Delete Technitium zones from the DNS page
A Delete zone button on the open zone of a Technitium provider deletes the zone and every record in it: the name has to be typed, and the server checks it against the zone as the provider lists it now (so a stale page, a wrong id or an internal zone cannot be deleted by mistake). What this app cached of the zone and its records goes with it. Technitium's own refusal is shown and nothing is changed. Administrators only, audited with how many records were cached; the adapter gets an optional deleteZone. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
0244f5a8ab
commit
082c524125
10 files changed
+197
-16
No files matched your search
@@ -80,7 +80,8 @@ All modules from the original plan are built:
|
||||
DNS, cPanel, and Technitium; providers are configured in-app (not via env
|
||||
vars) and their credentials are encrypted at rest. On a Technitium provider an
|
||||
administrator can also **make a zone** (Primary, Secondary or Forwarder — a name, or a
|
||||
network for a reverse zone), and Technitium's own refusal (a zone that exists) is shown as it was said
|
||||
network for a reverse zone) and **delete** one (its name typed to confirm; every record in it goes), and
|
||||
Technitium's own refusal (a zone that exists, a token that may not delete) is shown as it was said
|
||||
- **Servers** — cron/systemd tracking across Debian/Raspbian servers via a
|
||||
lightweight push agent (`agent/linux/`), Windows scheduled-task tracking
|
||||
through a PowerShell agent (`agent/windows/`, see its README), plus manual
|
||||
|
||||
Reference in new issue
Block a user