Skip to content

Knowledgebase

Preview and submit a cross-zone DNS operation

domain-nexus, development

The current REST bulk endpoints can check an owned selection and submit cross-zone work, but their preview is an informational summary. For a production integration that needs an exact reviewed record diff, use explicit per-zone changesets or the supported durable portfolio operation for that task.

Method Resource Scope Idempotency-Key
POST /v2/dns/bulk/preview dns:bulk Required
POST /v2/dns/bulk/execute dns:bulk Required

01 What the preview establishes

Provide between 1 and 500 owned zone IDs. The response identifies the selected zones, target count, an informational preview_id, an expiry time and whether the selection exceeds the small-batch approval threshold. It is not an immutable approval token or a complete comparison against each provider's live records.

The execute route accepts the requested selection again. It does not consume the preview ID as an approved, frozen plan. Your integration must therefore retain its reviewed target list and prevent accidental changes between review and execution.

02 Use the safe integration workflow

  1. Read each selected zone's current records, ownership and management state. Exclude a secondary or protected resource from an inappropriate record mutation.
  2. Build a concrete before-and-after change list for each zone, including existing record keys and row versions.
  3. Create individual changesets for the reviewed operations, validate them and obtain the required approval before applying.
  4. Persist each zone-to-changeset mapping so a partial failure can be reconciled without repeating successful work.
  5. For an operation supported by the portfolio service, use its durable preview, digest approval and per-item outcome workflow instead.

03 Current bulk contract limits

In this release, the documented bulk operation object and the worker's planner inputs do not align for all advanced verbs. The adapter does not forward every field required by the planner. The older update path also handles larger selections differently from immediate small-batch application. Do not build a mass delete, replacement or approval bypass by guessing fields from another interface.

Use the full DNS Manager bulk interface only for the operations it actually exposes and previews, or request a verified API contract for your installed release before enabling unattended bulk execution.

Common questions

Does receiving a preview ID mean records were validated?

No. It confirms the selected resources and summary, not a complete provider-level record plan.

Can I split a large unreviewed change into small requests?

Splitting does not provide the missing review or ownership checks. Use the changeset approval workflow and preserve a complete change record for the whole operation.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support