Export the source zone, preserve an original copy and review its origin, relative names, TTL values and mail records. Remove unsupported provider instructions only after recording what they did. DNSSEC signatures and provider-specific proxy, routing or traffic settings are not portable ordinary records.

Ensure the target zone exists under the correct account and provider package. Create a fresh backup if it already serves any traffic. Decide whether the import should add to current records or replace their editable set. Replacement can remove website, mail and verification data absent from the source.

1. POST to the zone's imports resource with content containing the complete text, format: "bind" and an explicit wipe choice.
2. Read the response and retain the import ID. Inspect parser errors, proposed records and conflicts instead of treating an accepted upload as a completed DNS change.
3. Read the stored import when resuming the workflow. Match its zone and source evidence to the intended change.
4. POST to /v2/dns/imports/{importId}/apply with the reviewed wipe value. Use a separate idempotency key for this apply action.
5. Track the resulting work, inspect the complete record list and test important names directly against the destination nameservers.

• Import DNS records from another provider
• Export BIND zone text and verify its SHA-256 digest
• Approve a current backup restore preview before changing DNS
• Approve, apply and verify a DNS changeset before reporting success
• Create an entitled DNS zone through the current API
• Change zone metadata and apply a management lock