Pre-load DNS for migration?

[RichBos]

Hi all, 

Got a quick DNS config scenario to check with the community.

I've got a client with multiple domains/sub domains we are migrating from a single fixed VPS to x2 Scalr managed farms across app/mysql roles, we've created all the app/domains/sub-domains & vhosts and am planning to pre-load the DNS in Scalr 'as is' (i.e pointing back at the existing servers) and then swap things to the Scalr farms when we're ready to go live.

My question is just this, obviously the A records in corresponding app/domain/sub domain entries will point back to the existing servers (pre change over) but in order for this to function correctly I'm presuming I leave blank entries for app (instance/role) allocation (until we swap over to Scalr managed).

Apologies if this seems like an obvious question, sometimes it's just better to ask though....!

Richard.

[Nick Toursky]

Richard,

I'd recommend creating a DNS zone in Scalr and pointing it to the farm. This will create all system records for roles, except the root record ('@').

Then create a static IN A record pointing to the current infrastructure.

Once you're ready for a switch, point DNS zone to the specific role on the farm, this will complement zone with root records pointing to servers of this role.

Then you'll need to delete static IN A record pointing to the old infrastructure.

Regards,

Nick

--
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/-/D9S2OQkivToJ.
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.

[RichBos]

Cool, cheers Nick, that's exactly what I needed to know, just wasn't sure about the pre-switchover farm/role allocation scenario.

As it goes timescales have slipped a touch (as they can) and we may be doing everything in one hit now anyway, however it's still very useful to know for future projects.

Thanks again.

Richard.