I have been looking around the internet and I have come across a few different ways to link my AWS EC2 instance to my domain name. It looks like I could do it using Route 53 but I am not entirely sure on that process. The other way is to map it from google. These seem like the best instructions I have found for that: link a Google Domain to Amazon ec2 server
The question that I can not seem to find is what about my email address. I pay google so that I can have some email addresses name#mydomain.com. Now these work fine and I have had them up and running for months. But now I want to have my website (it is a web app) point to it. Because currently when you go to mydomain.com it says This site can’t be reached mydomain.com’s server IP address could not be found.
Some help here on how to do this would be great. I am afraid that I am going to set this up incorrectly and then lose access to my gmail account which I cannot have happen.
Your domain's email is configured via MX DNS records. You would point your domain to your EC2 instance by adding A or CNAME DNS records. The two configurations are completely separate. You will not break your current email setup by adding an A or CNAME record that points to the EC2 instance. You simply need to add that record in your DNS settings, wherever your DNS is currently hosted. You don't need to make any changes in your Gmail account configuration, and you don't really need to use Route53 either (although it does add some nice features). You had to configure the MX records somewhere at some point, to setup your G-Suite account for your domain. You just need to go into that same DNS configuration (most likely still hosted at the company where you initially purchased the domain name) and add an additional record.
Related
Hej!
I own a domain registered through GCP and it's connected with Cloud DNS in GCP, I would be very happy if you could help me setup my custom domain for my web page at buahaha.github.io.
I think I know how to do this, because I did it before with other domain(s), but this time something is not working as it should. I have set up even a TXT record, and it does not propagate through DNS servers, and the same goes for my CNAME record. I attach screenshots of my setup below.
It's strange to me as it is the basic setup for this kind of service, and I'm really confused...
Pozdrawiam,
Szymon 🎶
In addition to #blacha answer, here are some links and guidance. Once you use Cloud Domain to register a domain, there is an option where you can use which DNS provider that you use for your domain. These are Cloud DNS, Google Domains and Custom Name servers.
If by chance you get confused which DNS server that you are using I suggest to DIG your domain to see which name server that you are using just to make sure you are using the correct DNS server.
Since this concern choses Cloud DNS here is the link that you can follow on how to create zone, configure A record connecting to the domains IP address and creating Cname record for the subdomain that you desire.
The problem was that I had to explicitly choose Cloud DNS as my DNS provider. If you have set your DNS zone already, just choose it from the drop-down menu, otherwise create your own...
I'm new AWS and I have to continue maintaining previous developer service that is hosted on AWS. The ec2 instance that is hosted has map to domain name of https://****c.k**g.g***an.org.au, however I couldn't find this domain name anywhere. I tried looking at route53, but there's no such domain name registered.
Please help, how do I find the domain name that is mapped to the EC2 instance? Where can I get that information. The reason because I want to deploy a new instance but with the same domain name.
Edit: Masking DNS for privacy reasons.
Are you sure your DNS is hosted by Route53? Running dig against k***.g****.org.au has the SOA held by ns1.mooball.net.
The whois for mooball.net returns register.com as the owner, so I would consider reaching out to your internal teams to see who holds that account, then check your DNS delegation settings by logging in to register.com.
Often times the client will control their own DNS, so it would also be worth confirming with your client where their root DNS (garvan.org.au) is hosted - you can then trace the subdomain delegation to see where it is ultimately hosted.
check route53 service in AWS , since the domain is served by https..it could be the domain mapped to a load balancer and the load balancer has the instance...anyway you can know from the route53 there you find all the records
So, this is my first time setting up a simple website and I decided to purchase a domain on Google Domains and I plan on hosting it on the AWS Free Tier plan. The domain was purchased last week. So, I am cannot transfer because the domain name is within 60 days of initial registration.
The goal is to create a simple landing page which uses a PHP script to generate a simple mailing list.
I have read this link 2-3 times already and followed all the steps:
https://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html
I want to keep all my G Suite features but I cannot because the guide asks me to copy AWS nameservers in my hosted zone to the DNS settings on Google Domains. This results in this.
I want to stick to AWS and not move to another hosting service, for certain reasons. Please guide me in the right direction. Thank you.
So I was able to fix this after I studied a bit and posted it on Reddit and got the answer.
Because we are working with subdomains, I made an S3 bucket with the subdomain name. I made the files public and generated the standard policy. Took the S3 bucket endpoint, and then went back to Google Domain's DNS settings.
I didn't need Route 53 in the first place. All I did was create a CNAME record with the subdomain and set TTL to 1 minute and the S3 endpoint as the data. And BOOM! It worked.
I believe when I move on to create more dynamic websites, I have to expand my search and learn more.
Thank you for everyone's help.
You can keep using Google Nameservers, along with hosting your website on you AWS Server (whatever the service you are using, like EC2, beanstalk).
Suppose if you are using an EC2 instance to host your server, make a note of its Public IP (I'd recommend using elastic IP). Now go to your google domain record set and create an A record with the IP of your EC2 instance.
refer https://support.google.com/a/answer/2579934?hl=en for details.
Using route53 is optional. It just helps you to store resource records. If you can create them somewhere else, Route53 is not required.
I'm working on transferring my website from godaddy, to AWS. I completed all the steps with the domain transfer, e.g. unlock domain, approve the transfer on both sides. And then I cancelled my Godaddy hosting. Now I have set up the AWS hosted zones, and I'm stuck on switching DNS services.
One of the steps is to enter the NS values on Route53 into the DNS provider on godaddy, but since I cancelled my hosting service I no longer have any way to access my DNS provider.
I'm wondering what to do in this situation. Is it possible to access the DNS provider directly? I waited for the TTL to expire before posting this because I thought that would fix my issues, but it did not.
If you transferred the domain registration to Route 53, you are following a set of instructions that doesn't match what you are trying to accomplish.
In Route 53...
Under "Hosted Zones," select your domain. Make a note of the 4 name servers assigned.
Then, under "Registered Domains," select your domain.
The name servers shown here need to match the 4 name servers that were assigned to your Hosted Zone.
Click Add/Edit Name Servers to modify them. They are probably still pointing to the Go Daddy (something like "nsxx.domaincontrol.com" if I remember correctly) name servers.
It sounds like what you were reading was instructions for moving your DNS hosting to Route 53, without doing a domain transfer, which is change of the registrar of record. Changing DNS hosting, only, would not have involved unlocking and approving as you described. Registrar and hosting are two completely separate services, but providers often bundle them together, leaving users often unaware of the distinction.
I am new in the Amazon EC2 world, I just created an app, that is located URL like this:
http://ec2-54-123-45-678.compute-1.amazonaws.com:8080
This is generated URL by Amazon EC2.
Now I would need to use my own domain name, so when I would access www.my-domain-name.com, I would like to see the content from
http://ec2-54-123-45-678.compute-1.amazonaws.com:8080
I bought the domain name on Godaddy.
Is there any way to do this in Amazon AWS dashboard or do I need to set it up in Godaddy system?
Thanks
I am answering on a more general level because I stumbled upon this thread when setting my custom domain.
In Amazon I created an instance and associated an IP to that instance. You were able to access it by typing in the amazon url
I actually used Media Temple not GoDaddy, but it will be similar. I went to the zone file and added that public url to the www
And as you can see, here is my blog actually working on the custom domain.
I set the wildcard because that way, no matter what someone types, if it is not set, then they will still see the site.
EDIT
For the root URL you should be entering your elastic IP and setting that as an A record.
First you need to set an ElasticIP for associated to that instance.
Then point the DNS entry of "www" for "my-domain-name.com" to the IP assigned in the step above.
Where you manage your DNS is another thing, can be in GoDaddy or in AWS Route53. You must adjust the delegation DNS in the "my-domain-name.com" register. Ex: your domain can be registered with GoDaddy but its delegation DNS point to Route53 so you can manage the domain from your AWS Console.
In order to setup DNS mapping you can map the existing IP 54.123.45.678 to ex: www.my-domain-name.com.
However, as you are running tomcat which is running at 8080 you need to forward the the request to the tomcat using Apache. So that you can visit www.my-domain-name.com without port 8080. If you are using linux box install Apache, apache-modjk and then configure sites.