I have a marketing website on wix with domain registered with godaddy, I've added a subdomain pointing to my EC2 IP for my app facing server, which works fine. Now I want to add a load balancer in front of that EC2 instance, however I cannot set the ELB A record in GoDaddy. Following this answer I created a hosted zone but if I change the name server I'll loose access to my wix website.
I want only the subdomain to point to my ELB while the main domain continues to point to the wix website, - do I need to change the name servers in GD to point to the aws hosted zone and then in the hosted zone map my main domain to the wix website and the subdomain to the elb? Do I need to move my domain registration to route 53 altogether?
What is the most recommended setup for this scenario?
Figured it out, writing for future help.
You need a hosted zone on route 53 pointing to the ELB, this gives you name servers. In GoDaddy add those name servers with your subdomain, keeping the existing name servers intact :)
Related
I have a couple of ECS tasks running in Fargate behind an ALB. I want to use a custom domain for the ALB so I created a hosted zone and an A record that points to the ALB but when navigating to the record name I get the "This page isn't working error". Is it mandatory to register the domain via the Route 53 or any other registrar or is the hosted zone and record enough for it to work? We have other ALBs with custom domains and when I navigate to the url the site comes up just fine. Settings look like mine so I am not sure if those are using a different registrar, which my hunch says they do.
Thanks for the help!
Is it mandatory to register the domain via the Route 53 or any other registrar or is the hosted zone and record enough for it to work?
The hosted zone is not enough for it to work. You absolutely have to register the domain with a domain registrar. You have to own the custom domain you are trying to use. You can use any registrar, not just Route53. You have to configure your Route53 hosted zone's NS records with the domain registrar before the hosted zone will work.
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.
I bought a domain with Google. I set up custom name servers to point the domain to Zeit.
Custom Name Servers
f.zeit-world.net
d.zeit-world.com
b.zeit-world.org
a.zeit-world.co.uk
Zeit controls the domain. I have spun up an EC2 instance with an elastic IP. I want to be able to point api.mydomain.com to the elastic IP using a CNAME.
added fake elastic ip just for example
now dns add mydomain.com api CNAME 194.119.279.121
I am not sure why it's not being resolved, obviously, I am missing some information. The URL api.mydomain.com just hangs.
Any insight into what step I am missing?
I have a domain registered with namecheap and its DNS records are managed by AWS Route 53. Currently the domain points to a regular EC2 instance. I'd like to get a subdomain set up pointing to a separate EC2 instance (specifically, an Elastic Beanstalk instance). I've got the Beanstalk instance set up (so if I visit the elastic IP for that instance, everything works fine).
THe problem is, all the docs I've seen on adding a subdomain to Route 53 imply that the parent domain's DNS records are still managed by the registrar. I'm unclear as to where I need to add the new NS records for the subdomain in order to have it point to the right thing.
Here is an example of a domain hosted at namecheap.com, DNS handled by route 53, website hosted on aws ec2 instance and the email server is hosted at Rackspace email.
Your situation is pretty close to this, so you should be able to follow this example and change to your specifics: