Make Technitium zones from the DNS page
A New zone form on a Technitium DNS provider makes a Primary zone (a domain name, or an address or network for a reverse zone), a Secondary zone (from the servers that hold it) or a Forwarder zone (where to pass questions, the protocol, DNSSEC). Names are written lower case, ASCII, without the trailing dot and refused before Technitium is asked if they are not zone names; Technitium's own refusal (a zone that exists) is shown as it was said. Administrators only, audited, and only for providers that can (the adapter gets an optional createZone). The new zone opens when it is made. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
f73704e6ca
commit
0244f5a8ab
12 files changed
+533
-10
No files matched your search
@@ -78,7 +78,9 @@ All modules from the original plan are built:
|
||||
a range on the spot; managing ranges from either page updates the other
|
||||
- **DNS** — zone/record management across Cloudflare, Loopia, Pi-hole, Azure
|
||||
DNS, cPanel, and Technitium; providers are configured in-app (not via env
|
||||
vars) and their credentials are encrypted at rest
|
||||
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
|
||||
- **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