Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

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'm currently trying to make record sets for a domain that is associated with an EC2 instance with an Elastic IP. I've followed Amazon's EC2 documentation, but trying to navigate to my domain doesn't seem to be working without the www prefix.

It works perfectly fine with the www prefix, since my A record points directly to the instance's Elastic IP. I've also tested trying to send emails to, which also works perfectly.

Here is how I currently have my record sets within Route 53 as well as the nslookup results of querying both domains.

I can't post the images, since I have less than 10 reputation, but I've linked them to the album below:

Are there changes that I need to make to my Route 53 record sets to get both domains to load the website?

share|improve this question
up vote 1 down vote accepted

You need to add a just plain record. Create a new A record and don't put anything in the subdomain box (where you put www for the record that does work). www and non-www are technically totally separate records, even if most URLs use them for the same thing.

share|improve this answer
Should I have this A record value as the Elastic IP, just like my A record with the www prefix? – user312268 May 23 '14 at 17:01
Great, that worked. Thanks! – user312268 May 23 '14 at 17:18

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.