Current DreamHost practices are to hard code Google Apps CNAMES – such as sites, calendar, etc. Depending on the hosting arrangement www. is either fixed to DH or fixed to Google Apps. The behavior of the naked domain is unspecified (see recent forum post on this, it seems to vary).
eNom allows more flexibility. All CNAME settings can be edited. So if I prefer to call use documents insted of docs I can (as long as I configure my Google Apps the same way). I can change www. Naked domains can go to www.domainname.com, etc.
Is there interest in asking DH for greater CNAME control? At least we ought to be able to edit the CNAMES for things that go to ghs.google.com.
I’d also like to do things like create a CNAME called “files” such that “files.mydomain.com” would resolve to a DreamHost directory. I don’t think that’s possible today.
tags: google apps, dreamhost, jfaughnan, jgfaughnan, DNS
tags: jfaughnan, jgfaughnan