Can Aws public hosted zone work without a registered domain?
I created a hosted zone for the domain name e.g example.com. keep in mind I don’t own nor register the domain name, I just used it for the hosted zone. Then I created the record to route traffic to my elasticbeanstalk application. It didn’t work.
Did it not work because I didn’t own the domain?
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 have a domain that's hosted by a hosting provider. I'd like to configure a subdomain of it to use an AWS elastic IP address I have that's used by an EC2 instance. Here's what I've done so far, but it still doesn't work.
Created an A record for the subdomain on the hosting provider's server
Created a Route 53 public hosted zone
Added an A record for the subdomain to the Route 53 zone
All routing policies in the zone are set to "Simple"
Created 4 NS records on the domain registrar for the subdomain that point to the Name Servers the Route 53 zone uses
When I ping it I get "cannot resolve sub.domain.com: Unknown host"
Am I missing something?
So I have a Hosted Zone(H1) for my Custom Domain Name for API-Gateway created via Cloudformation CDK initially.
Then I created a hosted zone(H2) for an ALB with the exact same domain name.
After creating the new hosted zone (H2), It seemed to overwrite the previous one (all traffic to the domain was going to the ALB) even though the previous Hosted Zone (H1) and its records still existed in Route 53 (untouched). Is this the expected behavior?
I ended up deleting (H2) but it did not renable the old hosted zone, now the domain is sort of just dead even though the hosted zone is still showing on Route53.
Yea I found the issue. My hosted zones were actually created for a subdomain in which a parent hosted zone delegated sub domain to my hosted zone via NS record.
I want to connect my domain (in AWS Registered Domains) to the IP address of my Ec2 instance in my AWS account; so that I can type www.my-domain.com in any browser and open my website.
I transferred a domain name from my old AWS account to a new one. Usually AWS creates a hosted zone for the domain automatically, but it didn't.
So I created my own hosted zone and and added and two A records (www.a.com and a.com) with value connected to the IP address of my Ec2 instance but the browsers didn't recognize the domain.
So I tried:
Updating the Name servers of the hosted zone to be the same as the domain name NS But same result
Updating the Name servers of the domain name to be the same as the hosted zone NS But same result
What can I do?
Thanks.
As long as the domain registrar is AWS (you can validate this by running whois against your domain) the setup should be quite simple.
Firstly it might be worth creating a new hosted zone if you've modified the NS records for it. It is important that these values are the original domains that AWS entered against the values. Also ensure the hosted zone is a public hosted zone.
Copy each of the nameserver values from your public hosted zone (there should be 4 in total). Then on your registered domain in the Route 53 console, edit the nameservers replacing the values with the values that were taken from your hosted zone. Once you have done this the new public hosted zone will be used by your domain.
Depending on any TTL caching you might find it can take a little time for clients to use this nameserver but you can test it by using a DIG command to find the NS value using an external server or the web service offered by google.
I don't know if this could count as and answer but this is what I did to fix the problem:
I created and Application Load Balancer
With Security Group with Inbound rules: HTTP TCP 80 0.0.0.0/0, ::/0
And Target Group TCP 80 Set to Ec2 instance.
Connect the A record to the ALB
This fixed my problem
In AWS, are you able to create multiple hosted zones for one domain? Say I have a domain called example.com.
In one account, I create a hosted zone for example.com and add the NS record to the DNS service.
In second account, I create another hosted zone for example.com and add the NS records to the DNS service for example.com.
1) Is this possible?
2) If it is, do I need to keep the record sets in the both hosted zones in sync with each other?
Yes. Creating multiple hosted zones allows you to verify your DNS setting in a “test” environment, and then replicate those settings on a “production” hosted zone. For example, hosted zone Z1234 might be your test version of example.com, hosted on name servers ns-1, ns-2, ns-3, and ns-4. Similarly, hosted zone Z5678 might be your production version of example.com, hosted on ns-5, ns-6, ns-7, and ns-8. Since each hosted zone has a virtual set of name servers associated with that zone, Route 53 will answer DNS queries for example.com differently depending on which name server you send the DNS query to.