I am attempting to set up a new website in AWS Lightsail and am unable to get my domain to point to my Lightsail instance. The domain was purchased in Route 53, and in that domain's hosted zone I have set up an A record to point to my instance's static IP. When I navigate to that static IP directly, I can access the site without issue.
These issues began occurring after attempting to create an SSL certificate in the Lightsail distribution tools. After configuring the distribution and DNS Zone, I edited the name servers in both the domain registry as well as the hosted zone in Route 53 to match what is recommended by AWS under the Lightsail DNS Zone information. It has been over two days since these name servers were changed, and I still cannot navigate to my instance through this domain.
Any suggestions even for how to troubleshoot this issue would be very much appreciated. Has anyone run into similar issues with Lightsail and Route 53?
I have a simple AWS setup of 2 VMs hosting a WebApp. An Application Load Balancer is in-front of these machines. I can access the DNS name of the Load Balancer and can reach to the WebApp.
Now, I want to connect to my app with a domain name hosted on Godaddy. I tried to simply create CNAME (as no Elastic IP on Application LB) with the LB's DNS name, but it didn't work.
What am I missing ? I tried with godaddy support but already wasted 7 days with not solution.
I want to put SSL certificate also on ALB. Should I be aware of anything specific in this setup?
The problem was, I was trying to CNAME for root level domain. Now, I created an alias in Route 53 and used AWS's nameservers on Godaddy to forward request there.
So I have an EC2 instance on AWS, associated it with an elastic IP; bought a domain (abstron.net) from Amazon, and tried to use route53 to route abstron.net to EC2.
I created a hosted zone, put in the domain name as abstron.net, created a new record, put the elastic IP (also tried public IP) without a name, but when I try to access abstron.net, it times out or does not load.
I am running a server on port 80 on EC2; the direct URL used for SSH works just fine. Any ideas? Thanks!
It is necessary to update the name servers of your Route 53 hosted zone with your domain registrar (abstron.net). Please update the same and try to access the website. This should work.
Thanks!
I've set up my application on AWS Elastic Beanstalk. I added a load balancer and pointed a CNAME for 'www' to it. But now I need to get root pointed there too. I can't use Route53 and use AWS nameservers because the client wants to use theirs. How can I get root to my app? Can I redirect the traffic? The tech lead I'm working with suggested setting up a server to do the redirect?
Since AWS ELB's only offer DNS Record (Instead of IPs) you need to use a CNAME mapping. However with DNS, CNAMEs do not allow root domain to point to it. To overcome this AWS has provided Alias Records (Custom implementation to AWS) to point root domain to ELBs.
If your client want to use their nameservers still you can use, AWS Route53 in between to solve this with following steps.
First create a Public Hosted Zone in Route53 for your domain.
Then create a record set inside the Hosted Zone for the root domain to point to the ELB with Type = A - IPv4 Address, Alias = Yes with ELB CNAME as for the Alias value.
In the external domain management service, create a NS record to point the root domain to Route53 nameservers.
Then when the DNS resolution happens, the root DNS query will first go to external nameservers(Managed outside of Route53) and then it will be forwarded to route53 where it will resolve the ELBs IP address and sent back.
You can set up a machine with a single static IP address that does nothing but redirect requests to the www host. Then you can put an A record on the bare domain at the apex of the DNS zone pointing to that machine.
There is at least one service, http://wwwizer.com/naked-domain-redirect, that will do this for you. (I'm not affiliated with this service, but it appears to do what it claims and will serve your purpose. There are probably others like it.)
Ideally, though, you'd persuade your client to change the authoritative nameservers to point to a Route 53 hosted zone that you create for them. They are still the registrant and "owner" of their domain, and can take control back from you by simply changing the nameservers to something else.
I generally persuade clients with the explanation that our load balancer infrastructure is integrated with the DNS servers so that if a balancer node fails, or we need to add or scale up capacity, or experience a traffic surge or DDoS event, the load balancer system will automatically update the DNS records for their domain to try to mitigate the issue and keep the site up. To do otherwise is to do things in such a way that removes those layers of redundancy.
Ideally, you can set up a apache server with a static IP, and install a free SSL certificate on that web server at first.
Second you need to redirect your root domain name request to AWS ELB.
Then go to your DNS management and set up your apex point to the server you created.
It is now possible to setup a Network Load Balancer and allocate one or more Elastic IP Addresses to it (one per Availability Zone). The Network Load Balancer can have an Application Load Balancer as a target. The Application Load Balancer would target the Elastic Beanstalk. An A record can then be created in the external DNS for each Elastic IP Address of the Network Load Balancer.
If you don't need the functionality that the Application Load Balancer provides, you may be able to target Elastic Beanstalk or whatever application directly from the Network Load Balancer.
Since AWS ELB's only offer DNS Record (Instead of IPs) you need to use a CNAME mapping. However with DNS, CNAMEs do not allow root domain to point to it. To overcome this AWS has provided Alias Records (Custom implementation to AWS) to point root domain to ELBs.
If your client want to use their nameservers still you can use, AWS Route53 in between to solve this with following steps.
First create a Public Hosted Zone in Route53 for your domain.
Then create a record set inside the Hosted Zone for the root domain to point to the ELB with Type = A - IPv4 Address, Alias = Yes with ELB CNAME as for the Alias value.
Quick Help Please....
I recently migrated my DSN from Godaddy to AWS Route 53. When doing the process I had checked "automatically import....". So I thought everything would propagate automatically.
Now after 7+ days when Godaddy finally released me, nothing is working. I am not an expert on DNS. And Site is down. Priority now is getting "www.example.com" to point to my ip address.
I have attached screen shot. What else needs to be done?
I should also add this was launched into a VPC.
Update I have attached an image of my Named Servers.
You shouldn't be using an IP address for S3. You need to change the record type to CNAME, and point it to the domain name S3 tells you to use. Honestly that's how it should have been set up on GoDaddy as well.
Here are the instructions: http://docs.aws.amazon.com/AmazonS3/latest/dev/VirtualHosting.html
You don't need to be an "expert on DNS" to set this stuff up. You just need to follow the instructions.
Also, when you say "this was launched into a VPC" what do you mean by that? Route53 offers public and private DNS zones. Public zones are similar to your previous GoDaddy DNS and are what you need to use for a public website. Private DNS zones are for DNS records you only want to resolve from within your VPC.