Use PD PowerDNS’s BIND-format tools to move reviewed DNS records into an existing editable zone or save its current data. An import adds values; it is different from restoring an earlier snapshot exactly.

Review the file and target

Keep the source file and confirm the intended provider and zone. Review website, mail, verification and child-zone records. The module preserves SOA and the apex NS set during import. Review any intended child-zone NS separately and handle signing outside an ordinary record import; secret DNSSEC keys are not transferred.

Import and read back

1. Open the intended zone’s Records view and its import control.
2. Paste or upload the reviewed BIND data.
3. Review the parsed input and exact destination before confirming.
4. Inspect the result and current record sets.
5. Compare all required values and TTLs with the intended configuration.

Before writing, the module compares the file with current records, collapses duplicates, skips matching values and excludes SOA/apex NS. Only missing ordinary values reach PowerDNS. Matching values are skipped even if the file TTL differs; adding a new value can still affect the shared name/type TTL. A conflicting single-value type, such as CNAME, needs review.

An import does not remove later values that are missing from the file. Reconcile the actual provider state after an uncertain result before repeating a write; do not treat every retry as harmless.

Export and complete a move

Use the available Export control to download the current BIND file. Keep it in appropriate private storage because zone data can reveal infrastructure and verification values.

Change registrar delegation only when the destination is ready and retain the previous service through cache transition. For rollback of an existing zone use the snapshot-restore guide, whose removal behaviour differs from import. Secondary-zone records must be maintained at their primary, not imported here.

Understand the record-data scope

The module reads and exports enabled record members of the types it recognises. Disabled members stored in native PowerDNS are omitted, so a module snapshot or BIND export does not preserve them. Record-set writes rebuild the affected set from enabled members and can remove disabled members of that same set. If your deployment uses disabled records, have your PowerDNS administrator preserve and review the native set through your authorised server process before a module edit, template, import or restore. A module safety snapshot is not a complete native-server backup.

Check the imported records

Your hosting team should compare the reviewed source, intended provider/zone, staged preview and original import result with actual enabled record sets. Import filters matching values and SOA/apex nameservers; it does not remove extra live values or update a matching value’s TTL, while adding another value can affect a shared TTL. Inspect an uncertain API result before repeating it. Do not repeat import to force an exact rollback.

See the PD PowerDNS WHMCS guide for related tasks, or explore PD PowerDNS.