I have a domain purchased in Google Domains.
I'm using Google Domains email forwarding, so I want to use Google Name servers only.
I'm hosting my website from AWS S3 and I've created Route 53 Hosted Zone for the domain I purchased in Google to setup my website requests to S3. I want to use Google Name servers in AWS Route 53 Hosted Zone.
I've tried editing the Hosted Zone and added Google Name Servers, but it didn't work.
Try looking at this doc:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/migrate-dns-domain-inactive.html
Looks like you need to set Route 53 back to the default name servers and then update google with those name servers.
Related
I am using AWS, route 53 service for creating Sub Domain. I need to create sub-domain for my elastic ip, i have created a hosted zone which is in public and attached a Name server and A record to the main hosted zone. while testing it doesnot respone my elastic ip.
example: Domain registration: example.com
subdomain: test.example.com
I rechecked it for 10 times the records, elastic ips are all correct,
In the main Hosted Zone i attached two records of subdomain A and NS, did i need miss anything?
Is the Domain purchased from AWS or 3rd party like godaddy/ hostgator? If purchased from 3rd party, check how to add NS records from 3rd party to AWS hosted zone.
Also, if your domain was purchased less than 24 hrs ago, wait few more hours for it to get propagated
Once this process is done, create A record for your sub-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.
I have a domain example.tld that is registered with one company and hosted with another. That website uses https and has a let's encrypt certificate setup by the hosting company through an automated script. I'm trying to an s3 bucket accessible from sub.example.tld.
I currently have a public s3 bucket and a CNAME setup with my hosting company to point sub to my bucket. I'm able to access the contents of my bucket from the http and https protocols using an Amazon generated domain, and from http only from sub.example.tld.
I know I can setup s3 with cloudflare and and use a cname with https there, however, since my domain name isn't hosted with aws I have to upload import a certificate which I do not have.
What I'm thinking of how I can proceed is to create a hosted zone in route 53 for sub.example.tld. Then I can delete the current CNAME registration with my hosting company to the bucket and instead create some kind of DNS record with my hosting company to point sub to the hosted zone with Amazon.
I'm able to create the following DNS records: A, CNAME, MX, NS, TXT, SRV, AAAA, DNAME, and CAA.
Does my idea of creating a hosted zone for the subdomain make sense? And if so, what type of DNS record would I create with my host to allow me to have a subdomain managed elsewhere?
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 worked with several godaddy domains in the past. But, for the new project infrastructure I wish to setup, I am planning on registering domain names from the new Amazon's Route 53 - Domain Registration.
My question is do I also need to pay for their DNS Service?
In the past I used to configure hosted zones (CNAME records) from the GoDaddy Console, but never payed anything extra.
How will relying on Amazon effect me in terms of cost and maintenance?
Update: Alright, looks like Amazon doesn't charge for DNS queries routed to their own internal services. Refer here: Route 53 Docs - DNS Service
If somebody is using Amazon Route 53 - Domain Name and their DNS, please let me know if/how you got charged for using their DNS Service.
From the documentation, notice the final step listed in registering a domain, when you want to use an external DNS hosting provider:
(Optional) Delete the hosted zone that Amazon Route 53 created automatically when you registered your domain. This prevents you from being charged for a hosted zone that you aren't using. (emphasis added)
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-register.html
Regarding other providers' pricing practices:
In the past I used to configure hosted zones (CNAME records) from the GoDaddy Console, but never payed anything extra.
That's fine, but you're looking at this situation upside-down. The two services -- domain registration and DNS hosting -- are separate services, but GoDaddy and many other registrars don't give you an option not to pay for DNS hosting, even if you don't use it -- it's built into their domain registration pricing. AWS tends to unbundle service components so that you only pay for the components you use.
If you are hosting services in AWS, using S3, CloudFront, or Elastic Load Balancer, you will find that Route 53's DNS hosting is the preferable option, because of the way resource records work at the apex of a domain due to the design of DNS itself. Route 53 is integrated with the other services to allow failover and redundant DNS configuration in a way that can't be accomplished with most external DNS providers.
Yes, you can use third party DNS service with domains registered in Route53 (you just have to add appropriate Name Servers)
About the pricing, it is all explained in detail here. Keep in mind that although queries to Alias records that are mapped to Elastic Load Balancers, Amazon CloudFront distributions, AWS Elastic Beanstalk environments, and Amazon S3 website buckets are free, that does bot apply to other AWS resources, including Amazon EC2 instances and Amazon RDS databases.
Also you will be charged fixed monthly amount for each hosted zone.