Use the module’s BIND-format import/export workflow to move ordinary record data into or out of a Route 53 zone. Treat it separately from registrar delegation and from AWS-specific routing or alias settings.

Prepare a source copy

Export the existing zone from its current DNS service and retain that file. Review website, mail, verification and subdomain delegation requirements before cutover. Check AWS-specific alias/routing settings separately: a BIND file is not a complete copy of every hosted-zone feature.

Open the intended hosted zone through AWS Route 53 DNS → Zones. If migrating into Route 53, create and populate the intended destination before changing the registrar’s nameservers.

Import into the reviewed zone

1. Open the zone’s supported import control.
2. Paste or upload the intended BIND-format records.
3. Confirm the target zone and review any displayed input/result information.
4. Apply the import and inspect the actual saved records.
5. Compare important names and values with the source file before completing a cutover.

The released Route 53 import adds supported records. It skips SOA and NS records, so do not assume a subdomain delegation was imported; review any required NS delegation separately. Existing values are not removed just because they are absent from the imported file.

Before starting, the module checks the planned import against the owning customer’s record allowance and refuses it if the allowance would be exceeded. A later AWS quota or permission refusal can still leave earlier records from the same operation already written. Reconcile the actual result before repeating an import. Do not treat repeated application as an exact replacement restore.

Export and finish the migration

Use the zone’s export/download control to save its current record file. Keep alias and advanced-routing details separately if those are part of the service, rather than assuming the file can recreate them elsewhere.

For a migration, update registrar delegation only after the intended destination is ready. Keep the old DNS answering through the cache transition and verify website/mail behaviour. See the hosted-zone guide for choosing the exact nameserver set and the snapshot guide for the released restore limitations.

Check same-named hosted zones before changes

If your AWS account contains multiple hosted zones with the same domain name, do not assume choosing a same-named row selects a particular hosted-zone ID. This module resolves zones by name. Have your AWS administrator compare the exact hosted-zone ID, records and delegated nameservers before using module writes; use AWS’s native zone-specific controls if the target remains ambiguous. Do not create or delete another zone to diagnose that ambiguity.

Check the imported records

Your hosting team should compare the staged input, owning customer’s record allowance and current destination records before another import. A preflight allowance refusal stops that import before provider writes; a later AWS refusal can leave earlier records already added. Check SOA/NS omissions, aliases and routing separately. Describe the affected rows without attaching the full customer zone file.

See the PD AWS Route 53 DNS WHMCS guide for related tasks, or explore the module.