Re: Vhost or Subdomain multiple farm confusion

[Nick Toursky]

Hi Richard,

First, a farm doesn't require a DNS zone to be assigned to it.

Second, the combination of what you've suggested is recommended: create DNS zones for TLD and all required subdomains and point them to the relevant farms/roles, then create corresponding virtual hosts and assign them to the app roles.

Hope that helps.

Regards,

Nick

On Tue, Nov 27, 2012 at 9:56 PM, RichBos <richbo...@gmail.com> wrote:

Hi, I'm getting somewhat confused with how Scalr DNS hangs together and wondered if anybody could advise. Here's what I require (which sounds easy but for some reason I can't seem to get my head round it today, it's either too much or not enough coffee....!)

I need to -

1. Create x2 server farms - i.e farm1 (Nginx balancer + x2 app servers + MySQL instance) and farm2 (no balancer, single app server + MySQL instance).

2. Host the TLD of the domain in Scalr with the main website (i.e 'domain.com') on farm1 along with a selection of sub domains (i.e one.domain.com, two.domain.com etc).

3. Host a selection of other sub domains on farm2 (from the same TLD), i.e three.domain.com, four.domain.com (etc).

My confusion is this, do need to - 

1. Create multiple subdomain 'domains' (alongside the TLD) and allocate them accordingly to the relevant farms? (Farms need a domain or domains allocating to them?).

2. Just create vhosts and point at the relevant app-servers?

3. A combination of 1 & 2?

...and, what extra (if any) DNS entries do I need to create (manually?) for any/all of the (correct( selection above?).

I'm reluctant to map anything to EIPs (although I seem able to get a degree of functionality by doing so), but if that's the way to go (by creating A records to EIPs) I presume for the Nginx balancer I'd allocate an EIP to that?

Just looking for the cleanest solution really, any advice appreciated.

Richard.

--
You received this message because you are subscribed to the Google Groups "scalr-discuss" group.
To view this discussion on the web visit https://groups.google.com/d/msg/scalr-discuss/-/5L4Smvg_eDYJ.
To post to this group, send email to scalr-...@googlegroups.com.
To unsubscribe from this group, send email to scalr-discus...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en.

[Rich Bos]

Hi NIck, yes, many thanks, that helps a lot to verify what I discovered later last night. Once I remembered Scalr DNS uses multiple entries for allocation (as oppose to how regular DNS works) it all made clear sense, i.e in the farm using an Nginx load balancer the DNS points to the Nginx role while the corresponding vhosts just point to the app role, in the single app farm everything (dns and vhosts) just point to the app role, easy...!

Thanks again for helping me out :-)
Richard.

--
cirronix  •  supporting the cloud

Amazon Web Services & Linux Server Solutions
call : +44(0)7960 196676 / email : r...@cirronix.com / web : http://cirronix.com
Old Broadcasting House, Woodhouse Lane, Leeds, West Yorkshire, LS2 9EN

[RichBos]

Hi NIck, yes, many thanks, that helps a lot to verify what I discovered later last night. Once I remembered Scalr DNS uses multiple entries for allocation (as oppose to how regular DNS works) it all made clear sense, i.e in the farm using an Nginx load balancer the DNS points to the Nginx role while the corresponding vhosts just point to the app role, in the single app farm everything (dns and vhosts) just point to the app role, easy...!

Thanks again for helping me out :-)
Richard.