DNS for every account, named profiles, enumctl 2026.10.1
enumctl 2026.10.1
- Keep separate configurations for different accounts or organizations with named profiles:
enumctl profiles create,select,list,get, anddelete - Use a profile for a single command with
--profile <name>, or for the current shell withENUMCTL_PROFILE - Removing a user also clears it from the profiles that pointed to it
- See the profiles reference
DNS
- enum DNS is available to every enum account, free of query and per-zone fees
- DNS calls return specific error responses, and listing the record sets of a zone that does not exist returns
404
Object Storage
- Names of deleted object storage users can be reused once the deletion finishes
- Creating a user with a name that is still being deleted fails with a clear error instead of conflicting
- Deletion errors now name the affected resource
- A bucket configuration that the storage backend rejects no longer replaces the last working configuration
API and SDKs
- New API documentation on authentication, HTTP and gRPC, errors, rate limits, and API clients
- Every docs page has a Markdown version at the same URL with
.md - The OpenAPI specification includes server and authentication definitions
- Enum fields are documented as the strings the API returns
- TypeScript SDK (
client-ts) adds astoragePoliciesservice