I'm in an AWS certification course where they don't respond to student questions. In the lecture we create an EC2 instance, then create an ELB and create a Hosted Zone for a domain name I purchased through AWS. This worked once, but now it's not working. The domain name I have registered doesn't resolve, but the ELB DNS domain name pulls up the web server as does the IP address.
What am I missing?
This answer actually came from "Michael - sqlbot" listed above but he never set it as an answer. I'm putting it here just so this question is answered, but he provided the solution.
https://serverfault.com/a/838396/153161
Related
I registered domain with AWS and set Hosted Zone.
inside the hostedzone i have NS with 4 records and SOA as a record type
I added A record type and point it to EC2 public IP.
in browser i can not get response when type domain name.i got "This site can’t be reached"
search here and some people advice to check NS with dig command.
dig command answered when i run in on Ec2 Ubuntu command but didn't get response when run it on my laptop.
I have other sites on roure53 but new one doesn't work.
any thought?
How did you registered the domain? Did you purchase it from a website and paid for it?
From what you said, it seems the FIRST thing you did was creating a Hosted Zone in Route53. Let me explain.
Usually when we purchase a domain from another website, after paying for it and everything we will need to tell the Domain Registrar to use the Name Servers and input a value like ns1.abcdomain.com and ns2.abcdomain.com . The purchase of a domain name usually comes with a free DNS service, so it will already have a valid name servers defined.
If my guess is correct, you created a hosted zone in AWS Route 53 without actually paying and registering a domain with a registrar (AWS is also a registrar). Therefore the domain only exist in AWS world because you created a Hosted Zone.
This explains why running dig on your EC2 provided the expected IP, because somewhere along the line the EC2 reaches AWS internal Route53 DNS service before reaching the public internet for DNS result.
If you indeed paid AWS something like $12 to purchase a domain, you might have misunderstood their interface (which can be confusing sometimes) and missed appointing Route 53 to be the domain's Name Servers.
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
I have a specific DNS problem for my website - I can access my website using its static ip address but not its domain name. Here's a description of my situation:
I registered a website name, say, "xxx.com", at GoDaddy.com, but the web app is hosted on a AWS lightsail Ubuntu instance with a static ip;
In the "DNS Management" page of this same on GoDaddy.com, I specified custom name servers as those provided by AWS
On AWS Lightsail, I then created an "A" DNS record that maps "xxx.com" to the ubuntu instance's static ip: "A" - "xxx.com" -> "x.x.x.x"
I was able to reach my website using "xxx.com" last night, but after rebooting the Ubuntu instance this morning, the domain name is unreachable while the website can still be accessed using its ip address
I have 2 questions -
How would AWS' name servers know that I am the rightful owner of this purchased domain name "xxx.com", by allowing me to map "xxx.com" to a certain ip address?
Did I miss something during the process above that made my website unreachable today using "xxx.com"? Why was it working yesterday but not today??
Any thoughts would be appreciated. Thanks in advance!
I can now partially answer my own question #2, and the answer is DNS propagation.
When DNS changes are made, it might take up to 24 hours for the DNS changes to take effect across the internet. Both name servers and one's local DNS cache will need to refresh first before receiving newly changed DNS records.
I have a simple question for pointing my Bigrock Domain name to Amazone EC2.
I have Created HostedZone from Hostedzone-create link
I got 4 name servers.
Now what?
Suppose my domain name is example.com on Bigrock.com.
Can anyone explain me how can i point that domain name to EC2?
I asked to Bigrock support but they told me something like this:
The website is not working because the DNS zone for your domain is not
configured properly on your Hosting providers DNS servers ( AWS Server
). Please get in touch with your provider for further assistance.
But I am not getting what they want to say. Please help!!
To move your Name Servers to AWS Route 53 first you have to change the Name Servers in Bigrock follow this steps.
http://support.hostgator.com/articles/hosting-guide/lets-get-started/dns-name-servers/how-to-change-name-servers-with-bigrock
Once that is done go to AWS Route 53 and create two record sets one for the "naked domain" and another for "www" domain and add a A-Record to point to the EC2 IP address (Be Sure the IP address is Elastic just in case for future change in IP address of the server so that you are covered).
This is Route 53 Guide
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/resource-record-sets-creating.html
Now, you will go to your bigrock.com and find your domain. Change the default name servers information with that 4 name servers information provided by Route53 on amazon. save your changes and wait for few hours to be activated properly.
It's been couple of days that I transferred my domain name from one AWS to another--dev environment to production. The problem is, the domain name isn't showing up in any DNS (Amazon or Google). I'm pretty sure I've configured the hosted zone correctly.
I'm also trying to verify SES which is failing and I also set MX records (Gmail) which don't work. The MX records and SES were set couple of days ago. Additionally, I created an A record to point to a elastic load balancer DNS name.
Any suggestions on what might be the problem? It's been couple of days and from past StackOverflow posts as well as past experience, DNS propagation on Amazon's server doesn't take more than 15 minutes.
EDIT:
Here is a timeline of events which can provide more information:
I had a domain abc.com on AWS account user1
The domain was transfered to AWS account user2
As of right now, the following hosted zone is created on user2's account:
The one thing this record set is missing is a CNAME to the load balancer which I had setup when the domain belonged to user1. However my understanding is that an A record should be good enough and it was a mistake on my part.
I'm using Windows and so I've flushed my DNS. I've tried looking up using AWS's DNS servers and Google's DNS server and nothing.
C:\>nslookup abc.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find abc.com: Server failed
It's been a couple of days since the domain was transferred. MX records were something I setup immediately and so I haven't gotten an email. If the DNS doesn't have any clue about the domain name, something must be wrong.
NOTE: The domain name is obfuscated to abc.com.
As suggested by #michael-sqlbot, the name servers were different in the console and hosted zone. I updated the name servers to the NS of the hosted zone. I see DNS propagation.