[Daniel15]

Edit your DNS records at NameCheap. You need to create an "A" record that points to your elastic IP. See http://www.namecheap...ds-for-a-domain for more information.

If you want email, you also need to set up MX records.

[JustinP]

I have my nameservers with route 53....is it basically the same but just do it through aws?

Edit:
This is how I have it set up:
On namecheap, I have it set to use custom DNS servers, and entered the four ones provided by amazon (http://d.pr/i/5UMg). Then, in route 53 I have 4 records. 1: NS record, value is the four DNS servers entered at namecheap (came with them) 2: SOA record, also default. 3: A record with the name of my naked domain, and value of the elastic IP. 4: same as three, but with name of domain with www.

I set it up like that friday evening, and whenever I try loading the page I get an error "Oops! Google chrome could not connect"

No idea what to do now :/

[ianonavy]

Why are you using the AWS DNS? You don't actually need to do that. If you change your nameservers back to Namecheap, you can just create an A record and point it to the IP address Amazon gave you as Daniel15 suggested.

[JustinP]

ianonavy, on 16 September 2012 - 07:32 PM, said:

Why are you using the AWS DNS? You don't actually need to do that. If you change your nameservers back to Namecheap, you can just create an A record and point it to the IP address Amazon gave you as Daniel15 suggested.

When I googled it that's what people said to do... I changed it, and i'm assuming that I need to wait until the TTL runs out for it to be visable?

The weird part is that when I put the IP address into the url bar it won't pull anything up... Is something wrong with my elastic IP?

[Daniel15]

Quote

have my nameservers with route 53....is it basically the same but just do it through aws?

That's fine, it's the same service except with Amazon instead of NameCheap. Amazon's DNS service (Route 53) does cost money though, so if you don't need its features (mainly high availability) you can use NameCheap's for free.

Quote

The weird part is that when I put the IP address into the url bar it won't pull anything up... Is something wrong with my elastic IP?

If you do an

nslookup

on the domain and it returns the correct IP address, the domain is set up correctly. If you can't even hit the IP address in your browser, it means there's something wrong with the IP. I don't have much experience with EC2 so can't help with this

[JustinP]

I'm stupid, I didn't realize I would need to install something like Apache on my EC2.

By the way, should I install Apache or something else?

[Daniel15]

Apache is good for a beginner since it's quite easy to get working and there's a lot of documentation and tutorials on it online.

You could also consider a different server like nginx, Cherokee, or Lighttpd. These have performance benefits over Apache and nginx is especially gaining popularity.

[JustinP]

So the guides I'm finding keep telling me to use yum to install it but I don't have yum already...so lost...

[Lemon]

JustinP, on 22 September 2012 - 05:55 AM, said:

So the guides I'm finding keep telling me to use yum to install it but I don't have yum already...so lost...

If you are on debian/ubuntu, use apt-get or aptitude instead then.

[Daniel15]

Which Linux distribution? If it's Ubuntu or Debian then you can do

apt-get install apache2

for Apache or

apt-get install cherokee

for Cherokee or

apt-get install nginx

for Nginx

[JustinP]

Okay! Got it installed! Im on Debian. The first time i tried installing it I got disconnected when confirming something and it was weird so I restarted my instance and tried installing again and it worked
Now I just need to set it up and scp a few files and hopefully it'll work