How to point my namecheap domain to my EC2 intance

Question

So far I found my way to Route 53 and it is probably what I need to use. So I found my way to a page called hosted zones and created a new Hosting zone, it asked for a domain name and i used the domain name I bought from Namecheap let us call it example.com. Continuing from there I saw that some record sets were already created one with the type "NS" and another with the type "SOA" I thought that the four NS values I got might be the ones I needed to connect to my Custom Namecheap DNS. I did so and waited a day and now and still nothing has happened. I have a feeling I am doing something wrong, which is why I ask for help now.

Accepted Answer

Hi,  
  
I just realized that you didn't mention creating any records of your own in your Route 53 hosted zone. That's how you specify that you want to route internet traffic for your domain (for example, artonn.com) to your resources. For information about creating records, see "Working with Records":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/rrsets-working-with.html  
  
If you're using an Amazon EC2 instance, see "Routing Traffic to an Amazon EC2 Instance":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-ec2-instance.html  
  
Scott

Answer

Hi,  
  
Yes, you'll want an Elastic IP address. That prevents the IP address of your EC2 instance from changing when you restart it. That's mentioned in "Routing Traffic to an Amazon EC2 Instance":  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-ec2-instance.html  
  
Scott

Answer

Hi Scott.  
  
What makes me a bit confused is, how does the route 53 hosted record that I made know to point the domain to my E3 Instance? I am running a web server on it.

Answer

Hi,  
  
Based on your description, you've taken the correct steps to make Route 53 the DNS service for the domain that you registered with Namecheap. It can take a couple of days for a change of DNS service to take effect because DNS resolvers typically cache your name servers for two days. For an explanation of how this works, see "How Amazon Route 53 Routes Traffic for Your Domain" in the _Route 53 Developer Guide_:  
  
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic  
  
Scott

Answer

Today my domain finally connected to the elastic IP. I can now access my website with the url, without problem. Thank you very much for your help, greatly appreciated.

Answer

Hi,  
  
If you post your domain name, I'll take a look at your DNS configuration.  
  
Scott

Answer

Thank you very much for the links Scott, I will check them out.  
  
I have hear people talk about elastic ip, is that something i need to do as well?  
  
- Artonn

Answer

Perfect thank you, Scott.  
  
I have created an A record, that contains my elastic IP associated with the EC2 instance in the value. I have used the NS values for my NameCheap DNS custom record.  
  
Am I all set up now, and it is only about time before my domain name points to my server?  
  
EDIT:  
  
I just checked my url today, and I am simply getting an "Cannot connect to this website" browser error.

How to point my namecheap domain to my EC2 intance

Contenido relevante