@opusdns/api 1.96.0 → 1.98.0

package/package.json

@@ -3,7 +3,7 @@
     "@opusdns/api-spec-ts-generator": "^1.2.0"
   },
   "name": "@opusdns/api",
-  "version": "1.96.0",
+  "version": "1.98.0",
   "description": "TypeScript types for the OpusDNS OpenAPI specification",
   "main": "./src/index.ts",
   "module": "./src/index.ts",

package/src/openapi.yaml

@@ -14990,7 +14990,7 @@ info:
     \n\n"
   summary: OpusDNS - your gateway to a seamless domain management experience.
   title: OpusDNS API
-  version: 2026-08-04-064134
+  version: 2026-08-04-135216
   x-logo:
     altText: OpusDNS API Reference
     url: https://d24lr4zqs1tgqh.cloudfront.net/c9505a20-5ae1-406c-b060-d392569caebf.jpg
@@ -32143,10 +32143,22 @@ tags:
     \ in the zone |\n| `PATCH /v1/dns/{zone_name}/rrsets` | RRset-level | Upserts\
     \ or removes entire rrsets by `(name, type)` |\n| `PATCH /v1/dns/{zone_name}/records`\
     \ | Record-level | Upserts or removes individual rdata values inside an rrset\
-    \ |\n\n### `PUT /v1/dns/{zone_name}/rrsets` \u2014 Replace all rrsets\n\nSupply\
-    \ the complete set of rrsets the zone should contain. Any existing user-managed\
-    \ rrset **not** in the request is removed. System-managed record types (SOA, DNSKEY,\
-    \ DS) are managed by OpusDNS and cannot be set or removed via this endpoint.\n\
+    \ |\n\nAll three endpoints refuse writes targeting rrsets you cannot manage. SOA,\
+    \ DNSKEY, DS, and the NS rrset at the zone apex are system-managed by OpusDNS:\
+    \ a payload rrset or patch op targeting one \u2014 upsert **or** remove \u2014\
+    \ is rejected with a `409` protected-rrset error (these rrsets are reported with\
+    \ `\"protected\": true` in zone responses). To change the nameservers a domain\
+    \ delegates to, update the nameservers on the domain instead.\n\nNS rrsets **below**\
+    \ the apex delegate a subdomain to other nameservers and are managed like any\
+    \ other record type, on all three endpoints and at zone creation. Two caveats:\
+    \ records (including domain/email forwards and parking) at or below a delegated\
+    \ name stop resolving publicly, because the delegated nameservers are authoritative\
+    \ for that subtree; and delegations from DNSSEC-signed zones are *insecure* delegations\
+    \ \u2014 child DS records are not supported, so the delegated subtree is not covered\
+    \ by the parent's chain of trust.\n\n### `PUT /v1/dns/{zone_name}/rrsets` \u2014\
+    \ Replace all rrsets\n\nSupply the complete set of rrsets the zone should contain.\
+    \ Any existing user-managed rrset **not** in the request is removed. System-managed\
+    \ rrsets cannot be set or removed via this endpoint; omit them from the payload.\n\
     \nUse this when you have authoritative, end-state data for a zone and want to\
     \ reset it to that state.\n\n### `PATCH /v1/dns/{zone_name}/rrsets` \u2014 Upsert\
     \ or remove whole rrsets\n\nSubmit an `ops[]` array where each op targets an rrset\