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?
Related
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.
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 :)
I currently have an sftp site setup on AWS where I can connect via Filezilla by providing the long AWS Public DNS name or the Public IP address(hostname) along with my credentials.
I have an existing domain abc.com which is hosted elsewhere(not aws). I want to use a sub domain such as sftp.abc.com to connect to my sftp site instead of the IP address.
Can I create the subdomain(sftp.abc.com) on AWS using Route53? If so, how do I accomplish this?
Would this affect my primary domain site abc.com ?
Anyone who can give me some advice on this would be helpful. Thanks
Create a hosted zone in Route 53 for the subdomain - e.g. sftp.abc.com. Amazon will specify 4 nameservers for the hosted zone. Simply go into your root DNS and create an NS record for the subdomain, specifying those 4 nameservers, and it should delegate authority for the subdomain to Route 53.
I have a static site on AWS S3 that I need to host on a custom domain. Unfortunately, that domain has already been registered on GoDaddy.
this article tells how to deploy S3 for custom domain:
Log into the Route 53 management console
Open your Hosted Zone
View the zone's record set
etc...
Unfortunately, my hosted zone is not available on S3 as it is on GoDaddy.
So I have 2 questions:
1) How can I point an AWS S3 bucket to a domain that is registered/hosted on GoDaddy?
2) That article says I need to attach it to a load balancer. Since it's a static S3 site, I never created a Load Balancer for it. How can I configure the domain if there is no LB?
To point your Godaddy domain to a S3 bucket you have to create a C-Name record for your domain www.dynamicdentaledu.com to point to your S3 bucket for www. See below screenshot.
And to point non-www domaindynamicdentaledu.com to non-www bucket see below.
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.