> 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?
As a CxO myself, I would be extremely reluctant to create CNAMEs that point to sites that actually belong to other organizations, as in your first example - I wouldn't want to imply ownership of support.microsoft.com. Nothing good can come from that. If your organization owns the hosted websites off campus, then I don't see any problem. Dave Watts, CTO, Fig Leaf Software http://www.figleaf.com/ http://training.figleaf.com/ Fig Leaf Software is a Veteran-Owned Small Business (VOSB) on GSA Schedule, and provides the highest caliber vendor-authorized instruction at our training centers, online, or onsite ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| 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:335760 Subscription: http://www.houseoffusion.com/groups/cf-talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/groups/cf-talk/unsubscribe.cfm
