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
Related
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
Currently I own a new VPS server and running my websites. For example I own www.auraquotes.com and that is running in this VPS server.
Currently I have issues with my hosting provider and I have switched to ovh unmanaged service provider. As the name 'unmanaged service provider' they will just help me in giving physical machines and that is all they will help.
how will I setup DNS server in my new VPS machine and adjust the nameserver settings appropriately?
Venkat.
DNS is a complicated service to set up and run, it is far easier to use an online DNS service, who will give you a nice web front end to configure things with.
The process is largely similar though, you need to configure your domain registrar with the name of your DNS server, or your DNS provider.
From there you configure the records you need and everything should work!
I need to set up a custom DNS server within EC2. I have one instance that acts as the DNS server, and N other instances that use this DNS server to connect to one another. Is this posible? Basically, I need to modify the DHCP settings for the N instances so that they connect to the DNS server. I can't find any good documentation on modifying the DHCP settings for an instance.
Note: I did find some documents, but they seem to only apply to Amazon VPC. Is there any way to do this without using VPC?
Short answer - no. You need a VPC. But once you have the VPC created - you can effectively do whatever you like with it.
Long answer - traditional AWS hosting gets an address directly from Amazon. This means you've got no control whatsoever of the IP addresses.
New accounts however come with a VPC by default, which means you can install a machine to act as a DNS server. (And I've done this in the past using Windows Active Directory)
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/
I have set up an EC2 instance and an Elastic IP which is associated to the instance. I have also set an A record in my DNS provider's Zone editor so that the domain name points to the elastic IP e.g. example.com = 123.123.123.123.
After reading many posts, this seems like it should be enough to work but my domain name still isn't resolving. I can't even ping the IP address! Weirdly I CAN ssh into the EC2 instance via the elastic IP and everything seems fine, except that my domain name doesn't resolve to the EC2 instance!
Any thoughts?
DNS names take a while to propagate so that is probably your first issue.
Go to http://www.whatsmydns.net/ and enter your domain name. If all of the locations are returning with the correct ip then you can safely assume its not a DNS propagation issue.
Enable ICMP rules in the security group. If using the aws console create a new rule for "All ICMP" with a source of "0.0.0.0/0". Enabling this creates a security risk for your server so only enable this temporarily while testing. At this point you should be able to ping your instance.
If using HTTP or HTTPS enable the correct ports on the security group for those protocols and as long as the instance is configured correctly with Apache you should be up and running.
Please check your EC2 security group & make sure desired ports are open