CNAME causing “Server Not Found” with AWS S3

I have a goDaddy site with a CNAME record set up to look at a specific bucket in my S3 account. It works fine and loads files without problem.

I have a server with SliceHost that has a CNAME record ("static") set up exactly the same as the one at goDaddy (with the domain name changed appropriately). When I attempt to access a file at the subdomain, however, I get a "Server not found" error. If I try to access the bucket file directly, it works fine.

dig and nslookup reveal that the subdomain is, indeed, eventually pointing at Amazon.

Here is what the ANSWER section of dig looks like:

static.imdoingscience.com.  2201    IN  CNAME   static.imdoingscience.com.s3.amazonaws.com.
static.imdoingscience.com.s3.amazonaws.com. 60  IN  CNAME   s3-directional-w.amazonaws.com.
s3-directional-w.amazonaws.com. 39  IN  CNAME   s3-1-w.amazonaws.com.
s3-1-w.amazonaws.com.   59  IN  A   72.21.207.241

I don't know if it matters, but the non-working instance is Ubuntu Hardy LTS running nginx. I don't think it should since a CNAME record seems to be a redirect at the nameserver level (I'm only just getting into this stuff).