I have a hosted zone and the accompanying record sets defined to serve a domain which lives in GoDaddy. I went to the AWS console today and found my hosted zone is no longer listed. However, it is still working and routing to my AWS server instance. Has anyone else see this issue in AWS? Any advice for finding my missing, yet working, hosted zone definition?
Double-check the account you use. Asking on AWS' own forums may get you some help from the employees.
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 have been trying to host our php website using Elastic Beanstalk however I had no luck under Hosted Zones. Domain is registered with the same AWS account.
Things I did:
Created a hosted zone named mycustomdomain.com
Created a A type record set with ALIAS to my environment. (Selected through drop down of AWS itself.)
The domain name of EB Environment
environmentname.randomclashofcharacters.region.elasticbeanstalk.com
assigned by AWS works flawlessly so I can say that there is nothing wrong with the config at Elastic Beanstalk side of things.
I followed through the guide uploaded by AWS themselves
I see one weird thing that might be causing that. The name servers listed under domain name is different from ones listed in Hosted Zone. Should I change them. AWS guide doesn't says to do so, so I didn't do it.
Thanks for your help beforehand.
Cheers,
~bio
Thanks to corrective help from #heplalump the problem is resolved. I actually needed to make domain's name-servers same with the hosted zones. Still cannot reach from desktop Safari but reachable via chrome and iPhone safari. If you want to do this procedure for yourself just follow the guide amazon provided.
I have recently bought a domain (caracara.es) with Route 53. It seemed to register all good and AWS created a hosted zone automatically for it.
I wanted to link it to the web hosted on S3 and as per instructions I created an A record and selected a bucket Alias from the dropdown (its set as web bucket etc.). That is the result:
The issue I'm having is that I don't seem to be able to access my domain from the outside world (I waited about 12 hours now) and I'm not sure how can I debug what's wrong with it... (ping says unknown host)
BTW, I have NS records, SOA records automatically created by AWS.
Would appreciate any help,
Thanks,
Michal
It turns out my domain was not setup correctly. The hosted zones NS automatically created by AWS didn't match the name server names of the domain itself.
Once I updated the domain to use nameservers from Hosted Zone - everything works fine.
Thanks for your help.
Michal
So I have been trying to figure out how to get my GoDaddy domain to link with my static S3 bucket so that I can host a static website using my domain.
The only guides I could find were for an Amazon hosted domain which I do not have.
I tried to figure out how hosted zones work and perhaps its my little understanding that is running me into road blocks trying to figure that out.
Do I use go daddy's nameservers and create a hosted zone record? I am very lost here and google is getting me nowhere.
Can anyone point me in the right direction?
So the problem here was the AWS guide was incomplete.
Also that I had changed the nameservers on the hosted zone in AWS.
If anyone is reading this, DO NOT CHANGE THE NS record ON THE HOSTED ZONE.
On AWS we have 2 Elastic Beanstalk instances and one S3 bucket for a static website. Since app used Login With Amazon we added https protocol. Recently we moved a domain to Route 53, created SSL certificates and configured Load Balancers with https for each of instances.
The website/elastic instances work well when addressed to generic by AWS domains.
But we faced with a problem when using the created domain on route 53. Sometimes domain is not available and we don't know why (see attached video). Failed to open route 53 domain
This issue reproduces on Safari when you refresh a web page many times and our servers become unavailable. We spent 1 week trying to fix this problem without any success. The real problem is that we don't even know what can be a reason. Any thoughts?
Thanks for any response!
As I can see from your domain informations you are pointing to an AWS IP-Address with an A-Record.
You should point your domain as "CNAME" to the AWS Url.
The IP of your Elastic Beanstalk Instances can change, the Elastic Beanstalk Url does not.
Greetings
Dominik
Resolved with this answer on AWS forum
https://forums.aws.amazon.com/thread.jspa?threadID=295461
Updated:
Unfortunately, the link is broken and I can't remind myself how it was fixed. It was a few years ago...