Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I registered a domain by Bluehost. However, I could not set up the domain correctly for Google sites at Bluehost:

alt text

Google's instructions

  1. Sign in to your domain hosting service and locate the DNS management page. The location varies by service, but can typically be found under Domain Management or Advanced Settings .

    1. Use the following unique string to create a new CNAME record for the domain:


    2. Point the CNAME record to:

    3. Once you have made the changes, you can verify that the record exists by doing a CNAME lookup for . You can find several web sites to do automated CNAME lookups by searching for CNAME lookup at

How can you assign a domain to Google Sites which is registered by Bluehost?

share|improve this question
related:… – Server Horror Jun 24 '09 at 23:29
up vote 3 down vote accepted

I used to use Bluehost and went through this exact scenario with them. They do allow some DNS control by the user, but to do what is required for Google Apps you'll need to call them and request for the changes to be made. They've done it a million times, so all you need to do is tell them that you're setting up a Google Apps domain and they'll likely know exactly what you want to have done.

I think it only took a few hours after the phone call before the changes were made and then another few hours for those changes to propagate.

share|improve this answer
Why does not Bluehost give you full permissions over DNS records such that you can set these settings directly in terminal by yourself? – Masi Jun 25 '09 at 0:00
The reason they gave me is that users kept messing with their DNS records, screwing stuff up and then calling them complaining that things didn't work right. So, instead of constantly fixing things for people, they decided to take away the ability for users to manage that themselves (which I can understand). I think they mentioned that they intended to give this functionality back to the user at some point, but perhaps with better instructions or something. – Justin Bennett Jun 25 '09 at 2:03

Use full DNS control or as you have listed above, point them to a public DNS server that you have control over. Most people don't deploy their own internet facing DNS servers now adays so what you will want to do is use bluehosts granulated dns configurations to create your records.

Most people will need to create an (A) record that resolves to a particular IP address. In all actuallity you need an (A) record before you can create a CNAME whether its on the same or a seperate domain name.

For instance if I have the domain registered, than I would need to create an '(A) record' in my 'forward lookups' for that particular domain which may have data in it like this:


Name: www


The host, would be listening on port 80 and/or 443 for my web requests. A CNAME record will most often require a pre-existing (A) record. In your case you would want to use what is provided by google for the CNAME which requires an alias and a fully qualified domain name for the fields.

ALIAS: googlea0406ece---


share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.