Take the 2-minute tour ×
Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

I have set up a CNAME record to point to an S3 bucket. It's been up for 4 days, and the results of a DIG Lookup show that it is in place:

;railroad.odehengineers.com.    IN  A

railroad.odehengineers.com. 3600 IN CNAME   railroad.odeh.s3.amazonaws.com.
railroad.odeh.s3.amazonaws.com. 60 IN   CNAME   s3-directional-w.amazonaws.com.
s3-directional-w.amazonaws.com. 3613 IN CNAME   s3-1-w.amazonaws.com.
s3-1-w.amazonaws.com.   60  IN  A

I created a test page test.html which should be visible from both:

But only the first, direct URL works. The other gives a 404.

Any thoughts? Do I need to coordinate at all with Amazon? Or am I just misunderstanding the purpose of a CNAME record?

share|improve this question

2 Answers 2

up vote 3 down vote accepted


share|improve this answer
I read this briefly before creating the CNAME, but didn't notice the requirement that the S3 bucket must have the same name as the CNAME. Thanks for pointing me there. –  Henry Jackson Nov 3 '10 at 3:32

It sounds like you need to configure host headers for the site to account for both URL's. Also, it's probably not the best idea to create a CNAME that points to another CNAME.

share|improve this answer
What do you mean "configure host headers to account for both URLs"? –  Henry Jackson Nov 2 '10 at 18:41
+1, it's a Host Headers (sometimes called Virtual Host) problem, it needs to be fixed on S3. Also, CNAME to a CNAMe isn't so bad, but piling them up will cause noticeable delays eventually. –  Chris S Nov 2 '10 at 18:47

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.