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 setup a CNAME record at my registrar (godaddy) and pointed it to my running instance located at ec2-204-236-164-223.us-west-1.compute.amazonaws.com.

I can't seem to browse, ping, or otherwise get any verification of the address using the IP, the name above, or the DNS/CNAME registrar redirect. Any thoughts on troubleshooting?

share|improve this question

Do you have any A records? The final A record translation has to occur in Amazon's cloud.

share|improve this answer
    
I'm redirecting straight to the ec2-204-236-164-223.us-west-1.compute.amazonaws.com address with a CNAME so that Amazon would maintain the actual IP address. I don't want to setup an Elastic IP just yet. I do plan to do so when I go live, but for now I just want to be able to view the site (or error the site displays) that is at the address ec2-204-236-164-223.us-west-1.compute.amazonaws.com. – Adron Nov 10 '10 at 17:17
up vote 0 down vote accepted

I finally got it to work by setting the @ name and CNAME. With just the CNAME the attempt to connect was failing over and over. But it's up and live now.

share|improve this answer

Your Answer

 
discard

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.