Use Hosted Zone of Route53 to another AWS Account

amazon-route53amazon-web-services

I have 2 AWS accounts A and B. There is a hosted zone my-domain.system in account A, which was originally created by AWS.

Now I want to create same hosted zone my-domain.system in account B, but don't want to migrate anything.

I tried to copy the nameservers of hosted zone of account B to nameservers of the account A, but that messed up the DNS, so I had to roll-back.

I want to achieve like, I created a record set in hosted zone of account B, it should work and I don't have to make changes in the account A's hosted zone.

Best Answer

The solution to this depends on who you registered the domain with. The domain registrar is where you specify the authoritative nameservers for a domain -- not in a hosted zone.

If the registrar is also Route 53, here's the process:

In the Route 53 console, click "Registered Domains."

Select your domain.

Choose "add/edit name servers."

Enter the values for the Route 53 name servers assigned to the new hosted zone in account B, which you'll see on the right side of the screen when you click on the row of the domain from the Hosted Zones page (don't click on the actual domain name, just highlight the row).

If you registered the domain with someone other than Route 53, you'll need to make the changes on that provider's admin console.

Related Solutions

AWS Route 53: How to migrate a hosted zone from one account to another completely

You can also use jq ("sed for JSON") to convert the JSON output of list-resource-record-sets to the JSON input to change-resource-record-sets:

jq '.ResourceRecordSets 
  |{"Changes":[.[] 
  |select(.Type!="SOA") 
  |select(.Type!="NS") 
  |{"Action":"CREATE","ResourceRecordSet":.}]}'

This assumes you have already created the new hosted zone and that it is empty except for the SOA and NS records, which are therefore removed from the JSON file. (The line breaks are for readability; remove them to use the command.)

Resolving route53 private hosted zone cnames internally

You will need to:

Setup IPsec VPN to connect between AWS and office, and
Setup Dnsmasq in both AWS and office sites to proxy your DNS requests.

The most important option of Dnsmasq in ths case is --domain=, to specify DNS domains to forward. You can use this option to pass DNS requests to your private Route53 domain (office clients -> Dnsmasq/Unbound in office -> Dnsmasq in AWS -> Route53).

Best Answer

Related Solutions

AWS Route 53: How to migrate a hosted zone from one account to another completely

Resolving route53 private hosted zone cnames internally

Related Topic