I got got a new domain that I want to link to aws.
I've already have EC2 instance running.
I'm using Route53 for DNS, and opened 2 records: www.domain.com and domain.com
I updated the register company about the new dns servers from route53.
I do have an elastic IP I linked to my EC2 instance.
the problem is that i can't reach my web site.
I guess I'm missing some parts.
did I miss anything along the way?
EDIT: I can reach my site using the public IP I got from Amazon.
But I can't reach it using my domain.
how can i tell what breaks it?
Some things to check:
Have you definatley set the namservers correctly with the domain registrar?
Have you added the elastic IP address in Route 53?
Some other things that you could possibly check are the firewall settings. This is unlikely the case if you can access the site via the IP address.
Do you know what IP address the domain is resolving to. Is this correct?
Also, you can have look at this blog it will explain lot of things
http://geekospace.com/mapping-aws-ec2-instance-to-your-domain-in-godaddy/
Related
I am a bit new to the deployment of a website. I have a server which is written in Node.js. Previously I had been using Heroku for deploying my apps without knowing much about deployment. I would like to know how do I deploy my server to create a website which has .com at the end of it like www.example.com and not www.example.herokuapp.com. I think it has something to do with domains (correct me if I am wrong). I would like to know what exactly is a domain and a DNS provider and how to deploy a website in such a way. Thank you.
You should ask one question to yourself when you hit www.example.com in browser how does it load a page?. When you run a website on your laptop it basically runs locally, if you want to access your website over the internet you would require public IP(host or server) accessible over the internet so you can access a webpage using public IP:port. But this is not the best option because IP may change in the future and also remembering IP for each application will be difficult. Imagine if you access Facebook, Instagram or any other websites by its IP addresses how difficult and inconvenient would it be? There are a couple of things you should know.
DNS-> Domain Name system
Every host is identified by the IP address but remembering numbers is
very difficult for the people and also the IP addresses are not static
therefore, a mapping is required to change the domain name to IP
address. So DNS is used to convert the domain name of the websites to
their numerical IP address.
DNS is a hostname to IP address translation service. DNS is a distributed database implemented in a hierarchy of name servers. It is an application layer protocol for message exchange between clients and servers.
Name servers
Domain Name Servers (DNS) are the Internet's equivalent of a phone book. They maintain a directory of domain names and translate them to Internet Protocol (IP) addresses. This is necessary because, although domain names are easy for people to remember, computers or machines, access websites based on IP addresses.
DNS record
A domain name, IP address what is the validity?? what is the time to live ?? and all the information related to that domain name.
Once you understand the DNS
Host(Deploy) your website to Amazon EC2 or Heroku and obtain Public IP.
Buy a domain from domain provider like Godaddy
Map domain(ie www.example.com to IP)-> DNS record
Mapping domain to IP may vary platform to platform but the Core principle remains the same. I would suggest you these below link. Try to find differences in both, doing so you will learn along the way
http://www.littlebigextra.com/map-domain-name-amazon-aws-ec2-instance/
https://medium.com/progress-on-ios-development/connecting-an-ec2-instance-with-a-godaddy-domain-e74ff190c233
Bluehost is my DNS provider and my app is hosted on heroku. I'm trying to point the DNS at my heroku app but there's an issue. Heroku's documentation states the following:
Some DNS providers will only offer A records for root domains. Unfortunately, A records will not suffice for pointing your root domains to Heroku because they require a static IP. These records have serious availability implications when used in environments such as on-premise data-centers, cloud infrastructure services, and platforms like Heroku. Since Heroku uses dynamic IP addresses, it’s necessary to use a CNAME-like record (often referred to as ALIAS or ANAME records) so that you can point your root domain to another domain. See examples below.
They go on to recommend creating a CNAME record with the values # and your root domain alias, e.g. hidden-sierra-7936.herokudns.com.
But Bluehost won't allow this because they want an IPv4 IP Address only and won't accept something like hidden-sierra-7936.herokudns.com as a valid CNAME record. I've already done the www record and things aren't working, so I'm guessing I need the ANAME record as well.
Is there any way around this other than switching to a new DNS provider?
Bluehost does not support this. Google and Cloudflare do, perhaps others. Cloudflare worked for me.
My first question ever. and newbie to webhosting.
I am trying navicosoft.com vps for the first time for webhosting. VPS just had centOS 7 on it. I installed ruby rails apache passenger etc and deployed my app. App deployed successfully. Here is the IP address http://88.198.121.97/ (site is still in production mode though). I also purchased domain dogtags.pk from http://pknic.net with its nameservers ns1.navicosoft.com | ns2.navicosoft.com. It has been over 72 hours since i registered for the domain.
I want to know what am I doing wrong? why is my site accessible via IP address and not by domain name? If i can get some link to a tutorial or documentation of some kind.
Customer support is very crappy. They are saying we dont provide any technical help for VPS. Help please. Thanks.
EDIT:
The best way might be to use a free DNS service (https://www.google.com/search?q=free+dns+service).
The setup would be as follows:
Use a free DNS service to point your domain name to the correct IP address.
Modify your domain name's nameservers to those of the free DNS service provider you've chosen.
For example, here's a link to how you can set this up with Namecheap's FreeDNS service: https://www.namecheap.com/support/knowledgebase/article.aspx/536/51/how-do-i-set-my-domain-to-use-namecheaps-freedns-service
If I ping my OpenShift application I see some IP like this
ec2-11-22-33-44.compute-1.amazonaws.com [11.22.33.44]
Can I be sure that my IP is 11.22.33.44 and I can use it for A record in DNS settings?
In which cases this IP is changed ?
Never seen this inforamtion. All articles claim that only CNAME may work.
You should never use an A record to point to your OpenShift application with an external domain. That IP address can change at any time for outage or maintenance reasons. You should always use a CNAME to point your domain name to your application url of the format app-domain.rhcloud.com
Just found an answer.
This was not just my own IP.
Several sites have this IP too.
http://www.bing.com/search?q=IP:11.22.33.44
I recently got an Amazon EC2 micro server to learn how to use nodejs. (I am not servers savvy BTW).
I managed to install everything and having nodejs running on the server and running their example script.
on Amazon I set the server security group to allow all / icmap - all/ tcp - 0-65535/ ssh/HTTP/HTTPS so basically everything is allowed more or less.
My question is how can I find my nameserver so I can use them on a new domain that I've bought.
I might be completely wrong and missing many steps if so. Do you know of a good tutorial on how to do that?
Thanks and sorry for the general question.
I believe what you want to do is point your domain to your new server.
You can do a couple of things in your domain registrar (where you bought your domain)
Add an A PTR record on your domain to point to the IP address of the server.
Add a CNAME record to point to the EC2 DNS name of your instance.
You can find the IP address and EC2 DNS name of your instance on the EC2 console:
You need to setup your domain name on Amazon's Route 53 DNS service in order to use their nameservers. Check out the link on how to retrieve the nameservers: http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html