Use PD Plesk DNS’s BIND-format controls to add reviewed ordinary records to an existing visible domain, or to save current record data. Import does not create the native domain and is different from snapshot recovery.

Prepare the target and input

Confirm the intended provider, Plesk account scope and existing domain. Keep the source file and review website, mail, verification and child-delegation requirements.

The shared import comparison skips matching current values, collapses duplicates and preserves SOA/apex nameservers before provider writes. It does not remove live values absent from the file.

Import and inspect

1. Open the existing zone’s Records page and its import control.
2. Supply the reviewed BIND data and inspect the preview and destination.
3. Confirm only the additions you intend.
4. Review the result and actual current record values.
5. Check authoritative DNS and the affected services separately.

Only supported record types can be written. Different conflicting values can still be refused, and writes are sequential; an error can follow successful earlier additions. Reconcile actual state before repeating an uncertain import.

Keep TTL and account recovery separate

The module does not send requested individual TTLs with record writes. Review the TTL guide before assuming a file’s TTLs were applied. A matching value is also skipped by import even when its source-file TTL differs.

Use Export to inspect or save current BIND-format data in appropriate private storage. An export is not a backup of hosting files, mailboxes, forwarding rules, account ownership or signing private keys.

If the domain itself is absent, use the domain-restoration guide before importing. For supported ordinary record rollback in an existing zone, use the snapshot guide.

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