DNS and subdomains

[David Allen]

We host a number of applications in a primary domain lets (foo.com).
DNS is managed internally for these domains (ns1.foo.com, ns2.foo.com).

I am migrating applications on a subdomain (sub.foo.com) to AWS with
Scalr (paid).

Any recommendations on how to configure DNS in this scenario?

-David Allen

[Alex Kovalyov]

Tick the "Use elastic IPs" for he www or app role (whichever it selected to
create A records). When your farm will be started and Ips assigned, add A
records in the zone on your namservers for each www(app) instance.
Auto-scaling of www role will not work in this case, b/c you do not know
what IPs will be assigned to newly started instances during up-scaling.

The practical example:
- use both www and app roles (or custom derived from them) in your farm.
Assume that www will not be scaled - set, say, 3 for both Min Instances and
Max Instances settings.
- Tick the "Use elastic IPs" for www role,
- Start a farm, write down IPs and enter them in your DNS zone.

[David Allen]

Interestingly - the Scalr images are not configured to use dns from
sclar.net. Meaning, I can't reference my database instances by the
DNS name because the authoritative server is not scalr.

Might be worth configing the ns for the images to point to scalr.net
rather than the EC2 DNS. Is this something that we can do ourselves?