AWS Route53托管区跨账户迁移可行性及保留NS/SOA的需求咨询

Hey there, great questions—let’s break this down clearly:

Absolutely! AWS fully supports moving Route 53 public hosted zones from one account to another. The process can be adjusted to either use new name servers or retain your existing ones, which is exactly what you need here since you’re closing Account A but want to keep your original NS and SOA records intact.

Since your goal is to keep the same NS and SOA servers while moving to Account B, follow these precise steps:

• Export all records from Account A’s hosted zone
  Log into Account A’s AWS Console, head to Route 53, and select your public hosted zone. Go to the "Records" tab, click "Export records" to download a CSV. This file will have all your custom records (A, CNAME, MX, etc.)—it won’t include the default NS/SOA, which we’ll manually carry over.

• Create a new hosted zone in Account B with your existing NS records
  Jump into Account B’s Route 53 console and start creating a new public hosted zone. Skip the auto-generated NS records—instead, paste in the exact NS server values from your Account A hosted zone. Then, manually copy over the full SOA record details from Account A: primary name server, admin email, serial number, refresh/retry/expire timings, and minimum TTL.

• Import your custom records into Account B’s zone
  In Account B’s new hosted zone, go to "Records" > "Import records" and upload the CSV you exported. Double-check that all your custom records are correctly imported—no missing entries here!

• Transfer the delegation set to Account B (critical step)
  Your original NS servers are linked to a delegation set in Account A. If you don’t transfer this, deleting Account A will take those NS servers offline. Here’s how to do it:

  1. In Account A’s Route 53, go to "Hosted zones" > "Delegation sets".
  2. Select the delegation set tied to your zone, click "Transfer delegation set", and enter Account B’s AWS account ID.
  3. Switch to Account B’s Route 53, go to "Delegation sets", and accept the incoming transfer request.

• Verify everything works before closing Account A
  Use tools like dig or nslookup to test that your DNS records resolve correctly. Since the NS servers are the same, you don’t need to update anything with your domain registrar—this is the beauty of retaining the existing NS setup. Once you’re confident all records are working as expected, you can delete the hosted zone from Account A and proceed to close the account.

• SOA Serial Number: Keep it identical to Account A’s initially. After migration, you can increment it for future DNS updates as usual.
• TTL Checks: If you had short TTLs set before, that’s fine—but since we’re keeping NS records the same, DNS propagation won’t be an issue here.
• Double-Check Delegation Transfer: Don’t skip this step! It’s the key to ensuring your NS servers stay active after Account A is gone.

内容的提问来源于stack exchange，提问作者dkakoti