Create, read, update and delete DHCP scopes and their lease reservations.
Manages DHCP scope/subnet configuration and lease reservations on whichever DHCP platform the caller is targeting, following that platform's own documented procedure exactly.
ipam-allocation for that. A platform like Infoblox may expose both concerns through related
objects, but allocating the address as inventory and configuring DHCP to actually lease it are
different operations; this skill is only the latter.There is no wire standard grounding management-API shape here the way RFC 1035/2136/1123 ground
DNS — RFC 2131 defines the DHCP protocol itself (what a client and server exchange on the wire), not
how a vendor's own API/CLI should represent scope or reservation configuration. Every platform below
designed that management surface independently. What is verified true across all three platforms
currently covered (Infoblox NIOS, ISC Kea, Microsoft DHCP Server — see references/INDEX.md):
range object is separate from its network object; Kea's subnet_cmds operate
on service configuration, not an inventory record; Windows's scope cmdlets have no IPAM-inventory
counterpart at all in this module. This is the basis for this skill's own boundary with
ipam-allocation — see "When to use this skill" above.fixedaddress, Kea's host
reservations, and Windows's DhcpServerv4Reservation are all separate create/read/update/delete
operations from their platform's own scope object, not a field on the scope itself.subnet4-update fully overwrites the subnet (anything omitted is
removed); Infoblox's range/fixedaddress updates and Microsoft's Set-DhcpServerv4Scope both change
only the fields explicitly supplied. Confirm the target platform's own update semantics in its
procedure.md before assuming either behavior.subnet4-del explicitly does not remove
associated leases/reservations, per its own documentation) — this is unverified
for Infoblox and Microsoft, so treat "does deletion clean up dependents" as
a per-platform question to check, not an assumed yes/no, before relying on it in an automated flow.See references/INDEX.md for which platforms have a procedure, and each platform file for how it
implements this shape concretely.
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. A
platform not listed there needs a new reference file before this skill can be used for it.ipam-allocation for that.procedure.md for the
specifics of what its file does and doesn't address.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/permitted client and call mechanism (WAPI, a JSON
command/response envelope over HTTP, or PowerShell/CIM cmdlets — not all of them REST) — see
references/INDEX.md for which, and that platform's procedure.md for the specific operations.
references/INDEX.md before proceeding, including its call
mechanism (REST-like WAPI, JSON command envelope, or PowerShell/CIM — not all are REST)procedure.md was followed, including its own confirmation gates on
destructive changes (scope deletion, which affects every active lease under it)