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.
Related
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?
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.
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.
I have an application deployed via amazon Elastic Beanstalk, and a domain bought on dataflame.co.uk
Now, what I want to do is to make the domain name on dataflame resolve to my application on Elastic Beanstalk.
I figured out that there's two ways I can do that:
1 - create an hosted zone on Route 53 and a traffic policy that will resolve the DNS to my EB application, and then modifying the NAME SERVERS pointer on dataflame to make it point to the Route 53 ones.
Cost of the operation: 50$/month
2 - migrate the domain from dataflame to Route 53, this is what amazon suggests, but then I still don't know if there will be the need to create an hosted zone with traffic policies even in this scenario.
Can somebody enlighten me on that? or hint some alternatives to me?
Route 53 contains 2 different services:
DNS resolution, and
Domain name registration
You can use both of these services, or one without the other. They are not dependent on each other.
DNS Resolution
If you want Route 53 to resolve your domain to your Elastic Beanstalk application, then you must create a hosted zone for it with appropriate record set entries.
Using Route 53, you could create CNAME records pointing to your EB app's endpoint. Or you could create an ALIAS record pointing to your EB app.
Costs for Route 53 DNS resolution is not $50 per month. The cost is $0.50 per hosted zone per month + traffic. See http://aws.amazon.com/route53/pricing/
Since dataflame also provides DNS resolution service, you could avoid Route 53 completely and use dataflame to resolve your domain name. To do this, you would create a CNAME entry in dataflame pointing to your EB app's endpoint.
Domain Registration
You can choose to transfer your domain from dataflame into Route 53, but this would be simply for registration purposes. You would pay for the transfer, then the annual domain cost (very similar to what you're paying at dataflame). If you do this, you still need to create a hosted zone.
If you want to keep your domain registration at dataflame, but you want to use Route 53 for DNS resolution, then you would edit your domain registration (in dataflame) and set the domain name servers to be those listed in your Route 53 hosted zone.
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: