CName URI Redirect problem...

184 views
Skip to first unread message

HeadOffice

unread,
Jan 17, 2011, 1:04:21 PM1/17/11
to gs-dis...@googlegroups.com
There seems to be something confusing in setting up the CName redirects text.

The text on the page here:

states that you need to create a bucket called travel-maps.example.com as well as a cname alias for travel-maps however if you try that then google just asks you to verify the domain without actually redirecting.

So - here's my problem...

1. I have a domain - let's call it example.com
2. I have hosted some static files in a bucket in google storage called site
3. I want to create a cname alias called cloud so that it points to my bucket.

So - I figure i need to create a cname alias called cloud which points to c.commondatastorage.googleapis.com
Then I should be able access my files by pointing to cloud.examples.com/site/inidex.html however this fails with an error #404

Can anyone point me in the right direction as to what I've missed?

Many thanks in advance...

Bob Oliver Bigellow XLII

unread,
Jan 17, 2011, 7:20:14 PM1/17/11
to gs-dis...@googlegroups.com
Your bucket name in Google Storage for Developers must be named something.example.com where "something" is some sort of name you want to come up with and "example.com" is your domain name that you have verified to Google that you own, using a number of different verification methods provided through Google Webmaster Tools.

Once your bucket, named something.example.com exists and you have verified that you own the domain, you'd create a CNAME record in your DNS for something.example.com to point to c.commondatastorage.googleapis.com.

So, in your example, if you want cloud.example.com/site/index.html to work... you'd need to do the following:

  1. Create a bucket named cloud.example.com
  2. Verify (using Google Webmaster Tools) that your Google Account has control over cloud.example.com
  3. Within the cloud.example.com bucket, create a "site" folder
  4. Put your static files (including index.html) into this folder
  5. Configure a CNAME record in your DNS to point cloud.example.com to c.commondatastorage.googleapis.com
  6. Visit cloud.example.com/site/index.html to test it out

It sounds to me like you are trying to circumvent the "verification" part. If Google didn't do this verification, there'd be nothing stopping anyone from creating a bucket called "cloud.example.com" when you own the rights to this. This would lock you out from creating a bucket with your own domain.

I hope this helps.

Nate Benes

unread,
Jan 17, 2011, 7:05:15 PM1/17/11
to gs-dis...@googlegroups.com
Are you absolutely sure you have the ACL set to public read?

On 01/17/2011, HeadOffice <peter.m....@gmail.com> wrote:
> There seems to be something confusing in setting up the CName redirects
> text.
>
> The text on the page here:
>
> http://code.google.com/apis/storage/docs/reference-uris.html#cname
>
> states that you need to create a bucket called travel-maps.example.com as
> well as a cname alias for travel-maps however if you try that then google
> just asks you to verify the domain without actually redirecting.
>
> So - here's my problem...
>

> 1. I have a domain - let's call it *example.com*
> 2. I have hosted some static files in a bucket in google storage called *
> site*
> 3. I want to create a cname alias called *cloud* so that it points to my
> bucket.
>
> So - I figure i need to create a cname alias called *cloud* which points to


> c.commondatastorage.googleapis.com
> Then I should be able access my files by pointing to
> cloud.examples.com/site/inidex.html however this fails with an error #404
>
> Can anyone point me in the right direction as to what I've missed?
>
> Many thanks in advance...
>

> --
> You received this message because you are subscribed to the Google Groups
> "Google Storage for Developers" group.
> To post to this group, send email to gs-dis...@googlegroups.com.
> To unsubscribe from this group, send email to
> gs-discussio...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/gs-discussion?hl=en.
>
>

HeadOffice

unread,
Jan 18, 2011, 11:07:19 AM1/18/11
to Google Storage for Developers
Nate,
Haven't got the bucket successfully create yet - see earlier reply...

On Jan 17, 7:05 pm, Nate Benes <natebe...@gmail.com> wrote:
> Are you absolutely sure you have the ACL set to public read?
>

HeadOffice

unread,
Jan 18, 2011, 11:06:58 AM1/18/11
to Google Storage for Developers
Bob,
Thanks for the response but it doesn't work - here's the problem...

(Assume I have example.com - though I'm using my own domain)

1. I created a bucket called cloud.exampple.com
2. When I try to verify the bucket - Google wants to...

a. Add a DNS configuration then checks cloud.example.com - but the
cname alias doesn't exist yet - so when I add the TXT record to my
domain Google tries to go to cloud.example.com and can't find it.
b. Adding a meta tag - but the cname alias doesn't exist yet - so when
I add the TXT record to my domain Google tries to go to
cloud.example.com and can't find it.
c. Upload HTML file - but the cname alias doesn't exist yet - so when
I add the TXT record to my domain Google tries to go to
cloud.example.com and can't find it.

I think I need to create the CNAME alias first and then verify but
that doesn't work eiither?




On Jan 17, 7:20 pm, Bob Oliver Bigellow XLII <iam...@gmail.com> wrote:
> Your bucket name in Google Storage for Developers *must* be named *
> something.example.com* where "something" is some sort of name you want to
> come up with and "example.com" is your domain name that you have verified to
> Google that you own, using a number of different verification methods
> provided through Google Webmaster Tools.
>
> Once your bucket, named *something.example.com* exists and you have verified
> that you own the domain, you'd create a CNAME record in your DNS for *
> something.example.com* to point to c.commondatastorage.googleapis.com.
>
> So, in your example, if you want cloud.example.com/site/index.html to
> work... you'd need to do the following:
>
> 1. Create a bucket named cloud.example.com
> 2. Verify (using Google Webmaster Tools) that your Google Account has
> control over cloud.example.com
> 3. Within the cloud.example.com bucket, create a "site" folder
> 4. Put your static files (including index.html) into this folder
> 5. Configure a CNAME record in your DNS to point cloud.example.com to
> c.commondatastorage.googleapis.com
> 6. Visit cloud.example.com/site/index.html to test it out
>
> It sounds to me like you are trying to circumvent the "verification" part.
> If Google didn't do this verification, there'd be nothing stopping anyone
> from creating a bucket called "cloud.example.com" when you own the rights to
> this. This would lock you out from creating a bucket with your own domain.
>
> I hope this helps.

On Jan 17, 7:20 pm, Bob Oliver Bigellow XLII <iam...@gmail.com> wrote:
> Your bucket name in Google Storage for Developers *must* be named *
> something.example.com* where "something" is some sort of name you want to
> come up with and "example.com" is your domain name that you have verified to
> Google that you own, using a number of different verification methods
> provided through Google Webmaster Tools.
>
> Once your bucket, named *something.example.com* exists and you have verified
> that you own the domain, you'd create a CNAME record in your DNS for *
> something.example.com* to point to c.commondatastorage.googleapis.com.
>
> So, in your example, if you want cloud.example.com/site/index.html to
> work... you'd need to do the following:
>
>    1. Create a bucket named cloud.example.com
>    2. Verify (using Google Webmaster Tools) that your Google Account has
>    control over cloud.example.com
>    3. Within the cloud.example.com bucket, create a "site" folder
>    4. Put your static files (including index.html) into this folder
>    5. Configure a CNAME record in your DNS to point cloud.example.com to
>    c.commondatastorage.googleapis.com
>    6. Visit cloud.example.com/site/index.html to test it out

Nate Benes

unread,
Jan 18, 2011, 11:32:35 AM1/18/11
to gs-dis...@googlegroups.com
Did you verify 'example.com' through google webmaster tools?

HeadOffice

unread,
Jan 18, 2011, 11:55:37 AM1/18/11
to Google Storage for Developers
Nate,
Yep - my 'root' domain (as in example.com) has been verified.
Still got the same problem though - Google wants me to copy a file or
add a TXT record for cloud.example.com but without the CNAME alias it
doesn't work as Google still tries to go there...

On Jan 18, 11:32 am, Nate Benes <natebe...@gmail.com> wrote:
> Did you verify 'example.com' through google webmaster tools?
>
> > > > gs-discussio...@googlegroups.com<gs-discussion%2Bunsu...@googlegroups.com>
> > .
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/gs-discussion?hl=en.
>
> > --
> > You received this message because you are subscribed to the Google Groups
> > "Google Storage for Developers" group.
> > To post to this group, send email to gs-dis...@googlegroups.com.
> > To unsubscribe from this group, send email to
> > gs-discussio...@googlegroups.com<gs-discussion%2Bunsu...@googlegroups.com>
> > .

Bob Oliver Bigellow XLII

unread,
Jan 19, 2011, 11:09:39 AM1/19/11
to gs-dis...@googlegroups.com
Have you tried creating the CNAME alias and TXT record to your DNS first, then validating?

Even though the CNAME won't properly resolve yet, I don't think the Google Webmaster verification cares where that CNAME record resolves to... it is likely only doing a DNS lookup to be sure the TXT record exists. If the TXT record exists, it will consider that you have sufficient control over the domain to be considered an owner.

Then, after the verification is complete, the CNAME record should start working after-the-fact.

If it still doesn't seem to work, you might try setting up cloud.example.com as a Google Site first. ( http://sites.google.com ) This will allow you to do the verification of the domain that way. Then, change DNS to represent the CNAME record Google Storage for Developers requires, and you should be golden.

I'm pretty sure adding the CNAME record before it's ready should still work, provided you are giving the DNS enough time to propagate before trying to check the validation.

HeadOffice

unread,
Jan 19, 2011, 9:06:50 PM1/19/11
to Google Storage for Developers
Bob,
That did the trick!! Thank you very much...

It seems I needed to create the CNAME alias as well as the TXT record
both for cloud.example.com AND THEN do the verification process the
following day (after DNS replication).
There was no problem after that.

Much appreciated - these forums offer a great service!
Thanks again...

On Jan 19, 11:09 am, Bob Oliver Bigellow XLII <iam...@gmail.com>
wrote:
> Have you tried creating the CNAME alias and TXT record to your DNS first,
> then validating?
>
> Even though the CNAME won't properly resolve yet, I don't think the Google
> Webmaster verification cares where that CNAME record resolves to... it is
> likely only doing a DNS lookup to be sure the TXT record exists. If the TXT
> record exists, it will consider that you have sufficient control over the
> domain to be considered an owner.
>
> Then, after the verification is complete, the CNAME record should start
> working after-the-fact.
>
> If it still doesn't seem to work, you might try setting up cloud.example.com
> as a Google Site first. (http://sites.google.com) This will allow you to

Bob Oliver Bigellow XLII

unread,
Jan 20, 2011, 4:53:25 AM1/20/11
to gs-dis...@googlegroups.com
Glad I could help!

Reply all
Reply to author
Forward
0 new messages