@opusdns/api 1.125.0 → 1.127.0

package/package.json

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

package/src/helpers/constants.ts

@@ -28,6 +28,7 @@ import type {
   DnssecDigestType,
   DnssecModeType,
   DnssecRecordType,
+  DnssecRegistryPublishOutcome,
   DnssecStatus,
   DomainAttributeKey,
   DomainAvailabilityStatus,
@@ -605,6 +606,22 @@ export const DNSSEC_RECORD_TYPE_VALUES = [
   'key_data',
 ] as const satisfies ReadonlyArray<DnssecRecordType>;
 
+export const DNSSEC_REGISTRY_PUBLISH_OUTCOME = {
+  PUBLISHED: "published",
+  DEFERRED: "deferred",
+  SKIPPED: "skipped",
+  WITHDRAWN: "withdrawn",
+  FAILED: "failed",
+} as const satisfies Record<string, DnssecRegistryPublishOutcome>;
+
+export const DNSSEC_REGISTRY_PUBLISH_OUTCOME_VALUES = [
+  'published',
+  'deferred',
+  'skipped',
+  'withdrawn',
+  'failed',
+] as const satisfies ReadonlyArray<DnssecRegistryPublishOutcome>;
+
 export const DNSSEC_STATUS = {
   ENABLED: "enabled",
   DISABLED: "disabled",
@@ -1812,6 +1829,8 @@ export const STATUS_TAG_TYPE = {
   INBOUND_TRANSFER_PENDING: "INBOUND_TRANSFER_PENDING",
   OUTBOUND_TRANSFER_PENDING: "OUTBOUND_TRANSFER_PENDING",
   EXTERNAL: "EXTERNAL",
+  IMPORT_REQUESTED: "IMPORT_REQUESTED",
+  IMPORT_PENDING: "IMPORT_PENDING",
 } as const satisfies Record<string, StatusTagType>;
 
 export const STATUS_TAG_TYPE_VALUES = [
@@ -1820,6 +1839,8 @@ export const STATUS_TAG_TYPE_VALUES = [
   'INBOUND_TRANSFER_PENDING',
   'OUTBOUND_TRANSFER_PENDING',
   'EXTERNAL',
+  'IMPORT_REQUESTED',
+  'IMPORT_PENDING',
 ] as const satisfies ReadonlyArray<StatusTagType>;
 
 export const SYNC_OPERATION_TYPE = {

package/src/helpers/keys.ts

@@ -1394,12 +1394,14 @@ export const KEYS_DNS_CHANGE = [
 
 export const KEY_DNS_CHANGES_CHANGES = 'changes' satisfies keyof DnsChanges;
 export const KEY_DNS_CHANGES_CHANGESET_ID = 'changeset_id' satisfies keyof DnsChanges;
+export const KEY_DNS_CHANGES_DNSSEC_REGISTRY_PUBLISH = 'dnssec_registry_publish' satisfies keyof DnsChanges;
 export const KEY_DNS_CHANGES_NUM_CHANGES = 'num_changes' satisfies keyof DnsChanges;
 export const KEY_DNS_CHANGES_ZONE_NAME = 'zone_name' satisfies keyof DnsChanges;
 
 export const KEYS_DNS_CHANGES = [
   KEY_DNS_CHANGES_CHANGES,
   KEY_DNS_CHANGES_CHANGESET_ID,
+  KEY_DNS_CHANGES_DNSSEC_REGISTRY_PUBLISH,
   KEY_DNS_CHANGES_NUM_CHANGES,
   KEY_DNS_CHANGES_ZONE_NAME,
 ] as const satisfies (keyof DnsChanges)[];

package/src/helpers/responses.d.ts

@@ -1145,9 +1145,10 @@ export type POST_DomainsByDomainReferenceDnssecDisable_Response = POST_DomainsBy
 export type POST_DomainsByDomainReferenceDnssecDisable_Response_404 = Problem;
 export type POST_DomainsByDomainReferenceDnssecDisable_Response_422 = HTTPValidationError;
 
-export type POST_DomainsByDomainReferenceDnssecEnable_Response = POST_DomainsByDomainReferenceDnssecEnable_Response_200 | POST_DomainsByDomainReferenceDnssecEnable_Response_404 | POST_DomainsByDomainReferenceDnssecEnable_Response_409 | POST_DomainsByDomainReferenceDnssecEnable_Response_422;
+export type POST_DomainsByDomainReferenceDnssecEnable_Response = POST_DomainsByDomainReferenceDnssecEnable_Response_200 | POST_DomainsByDomainReferenceDnssecEnable_Response_202 | POST_DomainsByDomainReferenceDnssecEnable_Response_404 | POST_DomainsByDomainReferenceDnssecEnable_Response_409 | POST_DomainsByDomainReferenceDnssecEnable_Response_422;
 
 export type POST_DomainsByDomainReferenceDnssecEnable_Response_200 = DomainDnssecData[];
+export type POST_DomainsByDomainReferenceDnssecEnable_Response_202 = DomainDnssecData[];
 export type POST_DomainsByDomainReferenceDnssecEnable_Response_404 = Problem;
 export type POST_DomainsByDomainReferenceDnssecEnable_Response_409 = Problem;
 export type POST_DomainsByDomainReferenceDnssecEnable_Response_422 = Problem;

package/src/helpers/schemas.d.ts

@@ -148,6 +148,7 @@ export type DnssecAlgorithm = components['schemas']['DnssecAlgorithm'];
 export type DnssecDigestType = components['schemas']['DnssecDigestType'];
 export type DnssecModeType = components['schemas']['DnssecModeType'];
 export type DnssecRecordType = components['schemas']['DnssecRecordType'];
+export type DnssecRegistryPublishOutcome = components['schemas']['DnssecRegistryPublishOutcome'];
 export type DnssecStatus = components['schemas']['DnssecStatus'];
 export type DomainAttributeKey = components['schemas']['DomainAttributeKey'];
 export type DomainAvailability = components['schemas']['DomainAvailability'];

package/src/openapi.yaml

@@ -2654,6 +2654,10 @@ components:
             type: string
           - type: 'null'
           title: Changeset Id
+        dnssec_registry_publish:
+          anyOf:
+          - $ref: '#/components/schemas/DnssecRegistryPublishOutcome'
+          - type: 'null'
         num_changes:
           title: Num Changes
           type: integer
@@ -3763,6 +3767,48 @@ components:
       - key_data
       title: DnssecRecordType
       type: string
+    DnssecRegistryPublishOutcome:
+      description: 'Fate of the DS/DNSKEY submission that follows signing a zone.
+
+
+        DEFERRED means the zone is signed but the parent holds no DS yet: the registry
+
+        rejected the submission because the public nameservers had not served the
+        new key
+
+        material yet, and a background job is retrying. A signed zone with no DS at
+        the
+
+        parent resolves as unsigned, so the intermediate state is safe.
+
+
+        WITHDRAWN means the zone stopped being signed while the DS was in flight,
+        so the DS
+
+        was taken back off the parent: the enablement did not take effect. It is kept
+        apart
+
+        from SKIPPED because SKIPPED also covers "there was nothing to submit", and
+        a caller
+
+        must not render an enablement that was undone as a success.
+
+
+        FAILED means the zone is signed and nothing is working towards a DS. Only
+        the zone
+
+        create path can report it, because that is the one caller that cannot propagate
+        the
+
+        error. Null means the response makes no statement about a registry DS submission.'
+      enum:
+      - published
+      - deferred
+      - skipped
+      - withdrawn
+      - failed
+      title: DnssecRegistryPublishOutcome
+      type: string
     DnssecStatus:
       enum:
       - enabled
@@ -12760,6 +12806,8 @@ components:
       - INBOUND_TRANSFER_PENDING
       - OUTBOUND_TRANSFER_PENDING
       - EXTERNAL
+      - IMPORT_REQUESTED
+      - IMPORT_PENDING
       title: StatusTagType
       type: string
     StrictMoneyDecimal:
@@ -15586,7 +15634,7 @@ info:
     \n\n"
   summary: OpusDNS - your gateway to a seamless domain management experience.
   title: OpusDNS API
-  version: 2026-08-20-103451
+  version: 2026-08-21-183123
   x-logo:
     altText: OpusDNS API Reference
     url: https://d24lr4zqs1tgqh.cloudfront.net/c9505a20-5ae1-406c-b060-d392569caebf.jpg
@@ -20016,6 +20064,59 @@ paths:
               schema:
                 $ref: '#/components/schemas/DnsChangesResponse'
           description: DNSSEC enabled successfully
+        '202':
+          content:
+            application/json:
+              examples:
+                dnssec_publish_deferred:
+                  description: Changeset response with `dnssec_registry_publish` set
+                    to `deferred`
+                  summary: DNSSEC enabled, registry publish deferred
+                  value:
+                    changes:
+                    - action: delete_record
+                      record_data: ns1.opusdns.com. hostmaster.opusdns.com. 2025111801
+                        10800 3600 604800 300
+                      rrset_name: example.com.
+                      rrset_type: SOA
+                      ttl: 3600
+                    - action: create_record
+                      record_data: ns1.opusdns.com. hostmaster.opusdns.com. 2025111802
+                        10800 3600 604800 300
+                      rrset_name: example.com.
+                      rrset_type: SOA
+                      ttl: 3600
+                    - action: create_record
+                      record_data: 256 3 13 5OmhbRQw0+xlqw4iYjM9SojiKkpfReE8LoMzzb3uDSvfvaePyreODC0Pf0eMti2hz/q9by5G7jh5nqQBRp8qAA==
+                      rrset_name: example.com.
+                      rrset_type: DNSKEY
+                      ttl: 300
+                    - action: create_record
+                      record_data: 257 3 13 4knSelKBhrAmgwkLMDbJGXmpdO2vkPf6uwGn52BQmlgWXjIXnGqv9CYPTwplRf4mRbFKFDkhU8dn9AsNOL+8EQ==
+                      rrset_name: example.com.
+                      rrset_type: DNSKEY
+                      ttl: 300
+                    - action: create_record
+                      record_data: 41074 13 2 0f8ad1e9b0de2eb958ba571208951e71330e6d9e2afa3c84ec6bd16d77bfc718
+                      rrset_name: example.com.
+                      rrset_type: DS
+                      ttl: 300
+                    - action: create_record
+                      record_data: 41074 13 4 f2fa86164e45235537238dd5b86a6a2533fd17b1e8216c1d66d18ccfc79be4dca77e3bc6d76eb136e193c2cee0a6ea85
+                      rrset_name: example.com.
+                      rrset_type: DS
+                      ttl: 300
+                    - action: enable_dnssec
+                    changeset_id: b89527a6-b46e-4d29-bd57-6a1b6b4915c7
+                    dnssec_registry_publish: deferred
+                    num_changes: 7
+                    zone_name: example.com.
+          description: The zone is signed, but the registry has not accepted the DS
+            record yet because it could not see the new key material on the public
+            nameservers. A background job resubmits it with backoff. Until it succeeds
+            the zone resolves as unsigned; if the job gives up, DNSSEC is switched
+            back off and a domain modification failure event carries the registry's
+            diagnostic.
         '400':
           content:
             application/problem+json:
@@ -20031,14 +20132,25 @@ paths:
         '409':
           content:
             application/problem+json:
-              example:
-                code: ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE
-                detail: DNS zone 'example.com.' is DNSSEC-enabled but has no usable
-                  DS records to publish
-                status: 409
-                title: DNSSEC Zone Records Unavailable
-                type: domain-dnssec-zone-records-unavailable
-                zone_name: example.com.
+              examples:
+                DNSSEC Enable Superseded:
+                  value:
+                    code: ERROR_DOMAIN_DNSSEC_ENABLE_SUPERSEDED
+                    detail: DNSSEC was disabled for 'example.com.' while it was being
+                      enabled; the DS record was withdrawn and DNSSEC is off
+                    status: 409
+                    title: DNSSEC Enable Superseded
+                    type: domain-dnssec-enable-superseded
+                    zone_name: example.com.
+                DNSSEC Zone Records Unavailable:
+                  value:
+                    code: ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE
+                    detail: DNS zone 'example.com.' is DNSSEC-enabled but has no usable
+                      DS records to publish
+                    status: 409
+                    title: DNSSEC Zone Records Unavailable
+                    type: domain-dnssec-zone-records-unavailable
+                    zone_name: example.com.
               schema:
                 $ref: '#/components/schemas/Problem'
           description: Conflict
@@ -25363,6 +25475,21 @@ paths:
                   Reference  Dnssec Enable Post
                 type: array
           description: Successful Response
+        '202':
+          content:
+            application/json:
+              schema:
+                items:
+                  $ref: '#/components/schemas/DomainDnssecDataResponse'
+                title: Response 202 Enable And Publish Dnssec Records V1 Domains  Domain
+                  Reference  Dnssec Enable Post
+                type: array
+          description: The zone is signed, but the registry has not accepted the DS
+            record yet because it could not see the new key material on the public
+            nameservers. A background job resubmits it with backoff, so the response
+            carries no records. Until it succeeds the zone resolves as unsigned; if
+            the job gives up, DNSSEC is switched back off and a domain modification
+            failure event carries the registry's diagnostic.
         '404':
           content:
             application/problem+json:
@@ -25379,14 +25506,25 @@ paths:
         '409':
           content:
             application/problem+json:
-              example:
-                code: ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE
-                detail: DNS zone 'example.com.' is DNSSEC-enabled but has no usable
-                  DS records to publish
-                status: 409
-                title: DNSSEC Zone Records Unavailable
-                type: domain-dnssec-zone-records-unavailable
-                zone_name: example.com.
+              examples:
+                DNSSEC Enable Superseded:
+                  value:
+                    code: ERROR_DOMAIN_DNSSEC_ENABLE_SUPERSEDED
+                    detail: DNSSEC was disabled for 'example.com.' while it was being
+                      enabled; the DS record was withdrawn and DNSSEC is off
+                    status: 409
+                    title: DNSSEC Enable Superseded
+                    type: domain-dnssec-enable-superseded
+                    zone_name: example.com.
+                DNSSEC Zone Records Unavailable:
+                  value:
+                    code: ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE
+                    detail: DNS zone 'example.com.' is DNSSEC-enabled but has no usable
+                      DS records to publish
+                    status: 409
+                    title: DNSSEC Zone Records Unavailable
+                    type: domain-dnssec-zone-records-unavailable
+                    zone_name: example.com.
               schema:
                 $ref: '#/components/schemas/Problem'
           description: Conflict

package/src/schema.d.ts

@@ -4752,6 +4752,7 @@ export interface components {
             changes: components["schemas"]["DnsChangeResponse"][];
             /** Changeset Id */
             changeset_id: string | null;
+            dnssec_registry_publish?: components["schemas"]["DnssecRegistryPublishOutcome"] | null;
             /** Num Changes */
             num_changes: number;
             /** Zone Name */
@@ -5431,6 +5432,26 @@ export interface components {
          * @enum {string}
          */
         DnssecRecordType: "ds_data" | "key_data";
+        /**
+         * DnssecRegistryPublishOutcome
+         * @description Fate of the DS/DNSKEY submission that follows signing a zone.
+         *
+         *     DEFERRED means the zone is signed but the parent holds no DS yet: the registry
+         *     rejected the submission because the public nameservers had not served the new key
+         *     material yet, and a background job is retrying. A signed zone with no DS at the
+         *     parent resolves as unsigned, so the intermediate state is safe.
+         *
+         *     WITHDRAWN means the zone stopped being signed while the DS was in flight, so the DS
+         *     was taken back off the parent: the enablement did not take effect. It is kept apart
+         *     from SKIPPED because SKIPPED also covers "there was nothing to submit", and a caller
+         *     must not render an enablement that was undone as a success.
+         *
+         *     FAILED means the zone is signed and nothing is working towards a DS. Only the zone
+         *     create path can report it, because that is the one caller that cannot propagate the
+         *     error. Null means the response makes no statement about a registry DS submission.
+         * @enum {string}
+         */
+        DnssecRegistryPublishOutcome: "published" | "deferred" | "skipped" | "withdrawn" | "failed";
         /**
          * DnssecStatus
          * @enum {string}
@@ -11325,7 +11346,7 @@ export interface components {
          * StatusTagType
          * @enum {string}
          */
-        StatusTagType: "VERIFICATION_REQUIRED" | "CREATE_REQUESTED" | "INBOUND_TRANSFER_PENDING" | "OUTBOUND_TRANSFER_PENDING" | "EXTERNAL";
+        StatusTagType: "VERIFICATION_REQUIRED" | "CREATE_REQUESTED" | "INBOUND_TRANSFER_PENDING" | "OUTBOUND_TRANSFER_PENDING" | "EXTERNAL" | "IMPORT_REQUESTED" | "IMPORT_PENDING";
         /** @example 12.50 */
         StrictMoneyDecimal: string;
         /** Support */
@@ -16787,6 +16808,15 @@ export interface operations {
                     "application/json": components["schemas"]["DnsChangesResponse"];
                 };
             };
+            /** @description The zone is signed, but the registry has not accepted the DS record yet because it could not see the new key material on the public nameservers. A background job resubmits it with backoff. Until it succeeds the zone resolves as unsigned; if the job gives up, DNSSEC is switched back off and a domain modification failure event carries the registry's diagnostic. */
+            202: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": unknown;
+                };
+            };
             /** @description Bad Request */
             400: {
                 headers: {
@@ -16809,14 +16839,6 @@ export interface operations {
                     [name: string]: unknown;
                 };
                 content: {
-                    /** @example {
-                     *       "code": "ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE",
-                     *       "detail": "DNS zone 'example.com.' is DNSSEC-enabled but has no usable DS records to publish",
-                     *       "status": 409,
-                     *       "title": "DNSSEC Zone Records Unavailable",
-                     *       "type": "domain-dnssec-zone-records-unavailable",
-                     *       "zone_name": "example.com."
-                     *     } */
                     "application/problem+json": components["schemas"]["Problem"];
                 };
             };
@@ -20893,6 +20915,15 @@ export interface operations {
                     "application/json": components["schemas"]["DomainDnssecDataResponse"][];
                 };
             };
+            /** @description The zone is signed, but the registry has not accepted the DS record yet because it could not see the new key material on the public nameservers. A background job resubmits it with backoff, so the response carries no records. Until it succeeds the zone resolves as unsigned; if the job gives up, DNSSEC is switched back off and a domain modification failure event carries the registry's diagnostic. */
+            202: {
+                headers: {
+                    [name: string]: unknown;
+                };
+                content: {
+                    "application/json": components["schemas"]["DomainDnssecDataResponse"][];
+                };
+            };
             /** @description Not Found */
             404: {
                 headers: {
@@ -20916,14 +20947,6 @@ export interface operations {
                     [name: string]: unknown;
                 };
                 content: {
-                    /** @example {
-                     *       "code": "ERROR_DOMAIN_DNSSEC_ZONE_RECORDS_UNAVAILABLE",
-                     *       "detail": "DNS zone 'example.com.' is DNSSEC-enabled but has no usable DS records to publish",
-                     *       "status": 409,
-                     *       "title": "DNSSEC Zone Records Unavailable",
-                     *       "type": "domain-dnssec-zone-records-unavailable",
-                     *       "zone_name": "example.com."
-                     *     } */
                     "application/problem+json": components["schemas"]["Problem"];
                 };
             };