IndigoAK
10-17-2007, 03:48 PM
Greetings,
I'm a recent former hosting customer of BlueHost.com, yet my domain is a still with BlueHost as a registrar. My issue is that since I am no longer with BlueHost as a hosting customer, technical support is making it difficult to manage my domain as a normal registrar would.
I contacted technical support last night because I've been trying to setup my domain to work with Google's Blogger service. Blogger has indicated to me that a domain needs a CNAME in order to work with their service, something that BlueHost administrators must create for the customer according to the technical support representative. The problem is that the tech support rep informed me that I need to be hosted by BlueHost for a CNAME to be create for my domain.
To be honest, this seems very counter intuitive. If I were being hosted by BlueHost, then I wouldn't need the CNAME in the first place. But since I'm no longer being hosted by BlueHost, I should have the option of having a CNAME created for my domain. After all, BlueHost has advertised that it's an ICANN accredited domain registrar.
My question is this:
Must I really transfer my domain to another registrar if I want a CNAME created for it, or was the tech support rep I spoke to simply misinformed about how BlueHost functions as a registrar for customer who still hold a domain with BlueHost, but no are no longer hosted.
I'm a recent former hosting customer of BlueHost.com, yet my domain is a still with BlueHost as a registrar. My issue is that since I am no longer with BlueHost as a hosting customer, technical support is making it difficult to manage my domain as a normal registrar would.
I contacted technical support last night because I've been trying to setup my domain to work with Google's Blogger service. Blogger has indicated to me that a domain needs a CNAME in order to work with their service, something that BlueHost administrators must create for the customer according to the technical support representative. The problem is that the tech support rep informed me that I need to be hosted by BlueHost for a CNAME to be create for my domain.
To be honest, this seems very counter intuitive. If I were being hosted by BlueHost, then I wouldn't need the CNAME in the first place. But since I'm no longer being hosted by BlueHost, I should have the option of having a CNAME created for my domain. After all, BlueHost has advertised that it's an ICANN accredited domain registrar.
My question is this:
Must I really transfer my domain to another registrar if I want a CNAME created for it, or was the tech support rep I spoke to simply misinformed about how BlueHost functions as a registrar for customer who still hold a domain with BlueHost, but no are no longer hosted.