Use PD cPanel DNS’s BIND-format controls to add reviewed ordinary records or save the current zone data. Import and snapshot restore have different effects.

Prepare the input and target

Identify the correct WHM provider and zone and keep the source file. Review website, mail, verification and child-domain requirements. The module import preserves SOA and the apex nameserver set; ordinary child-delegation NS records need their own review.

Import and read back

1. Open the intended zone’s Records page and its import control.
2. Supply the reviewed BIND data and inspect the preview and destination.
3. Confirm the intended additions.
4. Inspect the returned result and current records.
5. Compare the expected names, values and TTLs with authoritative DNS.

Before writing, the module collapses duplicate input, skips matching existing values regardless of TTL and excludes SOA/apex NS. Only missing ordinary values reach the provider’s supported-record writes. An existing TTL is not changed merely because its matching input value has another TTL.

Different conflicting values can still be refused. Provider writes are performed in sequence, so a later failure may follow earlier successful additions. Inspect actual state before retrying an uncertain import; it does not remove later values absent from the file.

Export and complete a migration

Use the available Export control to inspect or save current BIND data. Keep it private where it contains infrastructure or verification details. A record export does not preserve account ownership, forwarding configuration, secret signing keys or registrar state.

For rollback use the snapshot restore guide. For a DNS move, confirm destination records and delegation before retiring the previous service. Do not delete working DNS to force a refused import through.

See the PD cPanel DNS Blesta guide for related tasks, or explore the module.