My Goal this time is to make a script for AWS Marketplace that creates EC2 instances with Apache Httpd installed that are launched in different regions, and to set route53 to use a geo-location to open each server, also to sync one directory for content that will be universal and other that aren’t synced at all.
Leave Disquss comments below
Look at the new hosted zone you created for testing.example.com. This can be in the same AWS account, a different AWS account… any AWS account. There’s nothing here that is “account” related. This uses standard DNS configuration. The whole of DNS is a hierarchy. The global root can tell you where to find
com, and the
comservers can tell you where to find
example.com, and it’s nothing materially different for
example.comto tell you where to find
testing.example.cominstead of giving you a direct answer.
Note the 4 name servers that Route 53 assigned to the testing.example.com hosted zone. Verify that they are all different than the ones assigned to the example.com hosted zone. (For any of them to be the same should be impossible, but verify this.)
Now, back in the example.com zone, create a new resource record, with hostname
testing, using record type
NS, and enter the 4 name servers that Route 53 assigned to
testing.example.com, in the box below.
Now, when a request for testing.example.com and anything below it arrives at one of the Route 53 servers handling example.com, the reply will not be the answer from testing.example.com — the reply will provide the requester with the 4 NS records associated with testing.example.com and an answer equivalent to “I don’t know, but try asking one of these guys.”
The same concept should work for any legitimate Public DNS