One of the ramifications of relying on off-premise cloud infrastructure is that you’re necessarily stuck with some of the idiosyncrasies that come with it. For example, it’s not your network, and thus topologically-related identifiers such as host names and IP address are not within your purview. But you certainly aren’t going to ask your customers to visit “host111-east-virginia-zone3-subnet5.cloudproivder.com”. At least not if you want them visit, you won’t.
\nLuckily, you control your own DNS destiny, so you’ll just CNAME that crazy long host name provided by the provider to be something more catchy and inline with your branding, say, “coolappz.com”.
\nWhile certainly more appealing to everyone (easy to remember, fits better on a bumper sticker and on branded swag) it does have a downside: double the latency.<\/p>\n