Create, read, update and delete DNS zones, including SOA and NS settings and subdomain delegation.
Manages DNS zone lifecycle — creation, SOA/NS configuration, subdomain delegation, deletion — on whichever DNS platform the caller is targeting, following that platform's own documented procedure exactly.
dns-record-management for that. This skill's job ends where a zone exists and is correctly
configured; record-level content inside it is the other skill's concern.This skill has no single wire-level standard grounding zone lifecycle the way dns-record-management
can cite RFC 1035/2136/1123 for individual record semantics — zone creation, deletion, and SOA/NS
handling are managed very differently by each platform below, and only the following has actually been
verified true across all three currently listed:
dns-record-management assumes for individual zones.See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements zone lifecycle concretely — including where a platform's own behavior further narrows or
contradicts a generalization above.
platform argument. Check
references/INDEX.md; if no matching row exists, stop: this skill doesn't cover it yet.references/<platform>/procedure.md and follow it exactly — it contains that platform's
full operational procedure, error handling, patterns, known limitations, tools, and verification
checklist.references/INDEX.md (AWS Route 53, Cloudflare,
PowerDNS Authoritative Server) — a platform not listed there needs a new reference file before this
skill can be used for it.dns-record-management
for that.procedure.md for exactly which delegation shapes are documented versus flagged as unconfirmed.SKILL.md only changes for two reasons: a bug in the universal concepts/router logic above, or
adding a pointer to a newly-supported platform. Platform-specific procedure changes — a new error
code, a corrected field, a changed call mechanism detail — belong in that platform's own
references/<platform>/procedure.md, never here.
Each platform assumes its own authenticated client — see references/INDEX.md for which, and that
platform's procedure.md for the specific operations.
references/INDEX.md before proceedingprocedure.md was followed, including its own confirmation gates on
destructive changes (zone deletion, which removes every record inside it)