CNAMEs bring the advantage that you can change the IP address for the A record to which you are pointing and all the CNAMEs automatically move across. It's a lot less work for an internal resource and it's a good way to make sure that you're always pointing to the correct IP address for an external resource (it's how Google apps works with mail servers, for example).
-- WSS4CF - WS-Security framework for CF http://wss4cf.riaforge.org/ On 27 July 2010 20:48, Steve LaBadie <[email protected]> wrote: > > Is there any problem or disadvantage of creating CNAME in the DNS to > point to an outside domain or subdomain (i.e., > http://support.microsoft.com)? There seems to be resistance by the CIO > to use this naming convention and don't see what the problem is. I like > to use them to keep our identity intact when we have to host websites > off campus. We are currently developing a mobile site and I want to use > http://m.esu.edu but expect resistance. Any thoughts ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Order the Adobe Coldfusion Anthology now! http://www.amazon.com/Adobe-Coldfusion-Anthology-Michael-Dinowitz/dp/1430272155/?tag=houseoffusion Archive: http://www.houseoffusion.com/groups/cf-talk/message.cfm/messageid:335746 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
