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.
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.
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 have a domain for instance example.com.
The domain is hosted by a third party service (Digital Ocean).
I would like to give control of a subdomain to AWS.
So I would like to point aws.example.com to AWS.
Once the root subdomain is pointed to AWS. I would like to use Route 53 to setup the following functionality:
aws.example.com => alias to eb my-production-eb
dev.aws.example.com => alias to eb my-dev-eb
stage.aws.example.com => alias to eb my-stage-eb
Is this possible? Do I have to point my domains directly via cname record to the AWS load balancer?
Update 1:
I feel like I need to set the following in Digital Ocean:
aws.example.com => revoke control to AWS Route 53 somehow
*.aws.example.com => revoke control to AWS Route 53 somehow
Update 2:
The AWS documentation for Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain does not work for Digital Ocean.
Do not add a start of authority (SOA) record to the zone file for the parent domain. Because the subdomain will use Amazon Route 53, the DNS service for the parent domain is not the authority for the subdomain.
If your DNS service automatically added an SOA record for the subdomain, delete the record for the subdomain. However, do not delete the SOA record for the parent domain.
The question on Digital ocean regarding changing the SOA address titled "How can I change the SOA address in DNS settings?" states the following in one of the comments.
Unfortunately it is not possible to edit the SOA address right now
There is the ability to vote for this feature in Digital Ocean Configurable SOA record in DNS.
So my idea is that because you can't remove the SOA on Digital Ocean Amazon can't communicate to the domain correctly.
You need to delegate the DNS subdomain aws.example.com to Route 53.
See Creating a Subdomain That Uses Amazon Route 53 as the DNS Service without Migrating the Parent Domain
You can create a subdomain that uses Amazon Route 53 as the DNS
service without migrating the parent domain from another DNS service.
The basic steps are:
Create an Amazon Route 53 hosted zone for the subdomain.
Add resource record sets for the new subdomain to your Amazon Route 53 hosted
Update the DNS service for the parent domain by adding name server records for the subdomain provided in Step 1.
Assuming the current TLD example.com is hosted at Digital Ocean, then you need to create NS resource records there for the aws subdomain, using the name servers Route 53 provides you when create the hosted zone for aws.example.com.
Then you can control all hosts *.aws.example.com, including CNAMES for ELBs etc. from Route 53.
Yes, you can have any number of subdomains whether they are A or CNAME records, just point them to the target (public) IP.
I have a domain name registered with tmdhosting.com. And I have created a WordPress multisite setup on AWS using bitnami WordPress multisite stack.
Now I would like to point my domain name from my registrar to my AWS instance. Where they are asking me to provide them with a NS. I am new to AWS and I am not sure as to how to go about doing this.
Also did a little bit of research where it said that I will need a Route 53 (which is not free) I would want to know if there is another way to do this.
Can I use CloudFront to do this as with my previous provider had given me a cloudflare name server.
Please let me know the steps as to how to go about doing this.
To point a Domain Name to an EC2 instance, you can either use Route 53 or your own DNS service. In both cases:
Assign an Elastic IP address to your EC2 instance
In Route 53 or your own DNS service, define a domain/subdomain that points to this IP address
The above assumes that you wish to point to a single EC2 instance. If you have multiple instances with a Load Balancer in front, you will require a CNAME record pointing to the DNS name of the Load Balancer. (If using Route 53, using the "ALIAS" button to point to a Load Balancer.)
Route 53 is not free, but it is very cheap. If correctly configured to point to AWS resources, it can cost only 50c/month per hosted zone.
CloudFront is a content distribution network that caches web content. It will not assist you in assigning a Domain Name to an EC2 instance. (Custom domain names can be used with CloudFront, but that doesn't appear to be your particular question.)
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: