I had a use-case where I needed to use a subdomain and its Parent Domain already had a lot of DNS entries. So, it was very hard to manage 100+ DNS entries in a single account where you need to play with a single Subdomain. I found a solution wherein we could migrate a single Subdomain to another Domain Control (AWS) and thereby control all other Child Domains of that particular Subdomain separately. It will not make any changes to the Parent Domain, Parent will be untouched.
- Create a Hosted Zone entry in AWS Route53 for that Subdomain, eg: something.example.com.
- Copy NS Record of something.example.com.
- Create a new record of type NS in your parent Domain (example.com) account and put all NS records of something.example.com.
- Now all *.something.example.com will be controlled by the AWS Route53.
To check NS record for something.example.com you can try a few commands as below:
Check NS record of something.example.com:
➜ ~ dig NS +short something.example.com ns-1771.awsdns-29.co.uk. ns-389.awsdns-48.com. ns-747.awsdns-29.net. ns-1222.awsdns-24.org.
Check NS record of example.com:
➜ ~ dig NS +short example.com ns10.domaincontrol.com. ns09.domaincontrol.com.
Check stack trace for something.example.com:
➜ ~ dig +trace something.example.com example.com. 172800 IN NS ns09.domaincontrol.com. example.com. 172800 IN NS ns10.domaincontrol.com. ;; Received 128 bytes from 220.127.116.11#53(18.104.22.168) in 470 ms something.example.com. 1800 IN NS ns-1771.awsdns-29.co.uk. something.example.com. 1800 IN NS ns-747.awsdns-29.net. something.example.com. 1800 IN NS ns-1222.awsdns-24.org. something.example.com. 1800 IN NS ns-389.awsdns-48.com.
Other Use Cases:
- If you have multiple vendors and each one wants full access on its Subdomain, you can easily distribute Subdomain on the different account and give complete access.