On Nov 6, 7:54 pm, Keenan Brock <[EMAIL PROTECTED]> wrote:
> Hi Mirko/all,
>
> Sorry to keep the thread alive
>
> Nothing is preventing you from pointing mydomain.com at Heroku as an a
> record/ ip address.
Actually, there are two things.
> They suggest using a cname so that you won't be affected by an ip
> address change.
This is one of them, although admittedly only a minor reason, as I
assume that Heroku's IP addresses probably aren't that likely to
change.
The other reason is that heroku.com actually resolves to two IP
addresses, so they're using DNS Round Robin. By pointing my A-record
straight to one of these IPs, I bypass this mechanism. I'm not sure
how critical this is for their load balancing architecture, but this
could potentially be an issue. For example they could conceivably use
this mechanism for rolling upgrades, by taking one of the IPs out of
rotation, then adding it back in after the upgrade is completed.
-Mirko
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Heroku" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/heroku?hl=en
-~----------~----~----~----~------~----~------~--~---
