Ok rather than me ask what I'm doing wrong, like you a have a crystal ball or something, how about "How do I use Turnkey and EC2 to have a development instance that is a clone of my tkl sub-domain instance that will not affect my sub-domain instance when I make changes to the development instance?"

I tried cloning a server in TKL and had these problems so I created an AMI with an attached EBS volume that is not destroyed each time it is stopped or terminated. Then I created a clone of that. Turns out that the new instance picked up the TKL subdomain even though hub is not aware of the new instance.

I'd still like to have this working through TKL rather than cloning through EC2 directly so if anyone can give me any tips on doing so I'd much appreciate the information.

Anytime I create a clone of a server the sub-domain for tklapp.com moves over to the new server? Damn, this stuff can be frustrating.

When I create a clone of an instance the innisfree.tklapp.com sub-domain becomes associated with the new instance IP. When I re-associate the name with the original instance it reverts itself back after a period.

2 Questions about tklapp.com sub domains

1. How do I make the tklapp.com subdomain sticky to one instance?
2. Can I create another tklapp.com sub domain to point at my development server?

For now I just moved on and used a couple of "A" records with my dyndns account. Thank you though, that is something I will need to deactivate or better yet remove as it will not be needed.