I've deleted a route 53 hosted zone, but before I made a backup of values of all NS,SOA,A,AAAA servers. Now I'm trying to recreate that zone with the same values and it does not work. I get "DNS_PROBE_FINISHED_NXDOMAIN" error on my google chrome.
I solved it. It seems you can't use your old name servers, so I just recreated my hosted zone and copied the new name servers to my domain settings page (below).
Related
I bought a domain through Route 53, oproponitis.com, I have an elastic beanstalk enviroment that works fine, I can open the page through the EBS url. I have a hosted zone where with A record simple record redirecting to this environment, but when I open the page it gives me DNS_PROBE_FINISHED_NXDOMAIN, it drives me crazy as I cant find info about it anywhere, and it is a pretty simple setup.
Any idea what is maybe going wrong?
update
This is as a result of a DNS lookup failing for your Name Servers.
As you purchased your domain in Route 53 and also have a public hosted zone in Route 53 this should be an easy solution to fix.
In the AWS console access your public hosted zone and make a note of the values of the NS record (there should be 4 domains).
Then in the Route 53 console do the following:
Access the Registered Domains link.
Click on your domain
Click Add or edit Name Servers
Specify the values of each of the values you copied earlier from the NS record.
I had the same issue and the problem was that I didn't verify my email.
I am new to AWS and facing this issue for the past few days. So any help will be appreciated :)
I have created an AWS EC2 instance and deployed backend&frontend services on SINGLE INSTANCE that are used in my project.
Backend->Java,Apache tomcat,RDS,Elasti cache
Frontend-> Node
And now created a hosted zone under Route53 to host my Namecheap domain in AWS EC2.
Have checked all configs thrice, and added A type(Value as ec2 IP) and CNAME(Value as domain name e.g. xxyyzz.liv) type variables in the hosted zone including modifying nameservers from hosted zone to the Namecheap DNS settings.
Even after long waiting(of 48 hrs) my domain is not getting live, tried multiple times but no help.
This will be caused by misconfiguration. Perform the following steps to rectify this issue:
Ensure you have not replaced the NS or SOA records in Route 53, these should stay as the values that Route 53 generates. If you have replaced their values, create a new public hosted zone and migrate the records to this (excluding NS or SOA).
Run DIG against your domain for the MX record, either by running DIG NS example.com or by using an online tool such as https://toolbox.googleapps.com/apps/dig/. If you get no results back (returning a SERVFAIL) or incorrect name servers back then you will need to update the name server configuration.
Within your public hosted zone in Route 53 look for the NS record, copy the values (there will be 4 nameservers). Then within namecheap follow these instructions for "Custom DNS". Add each name server from Route 53.
By now running DIG again you should be able to see the records that should have previously been accessible. Depending on the TTL of the previous NS record you might find it takes a few hours/days for the DNS to migrate across, although you can clear the DNS cache on your local network.
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
I have an Amazon EC2 instance on AWS associated with an ElasticIP. I purchased domain from Route 53. It automatically created the Hosted Zone.
It worked fine after creating a Record Set for the domain name.
I have deleted that Hosted Zone but when I add it again, it is not working. What am I missing there?
When you delete a hosted zone and then put it back, you're not exactly putting it back. You're just creating one similar to (but not identical to) the original.
So don't do that. But, since you already did, here's the fix:
When you click on a domain in "Hosted Zones," you see 4 name servers assigned to the hosted zone by Route 53 on the far right side of the screen.
Each time you create a hosted zone, these 4 values will almost always be different -- meaning that your hosted zone now lives on 4 new, different authoritative name servers in Route 53 than the ones it was previously deployed on, when you were using the old hosted zone.
But the Internet is still expecting the old 4 nameservers to have your records... which they don't, because you deleted the original hosted zone.
You have to update the authoritative nameservers with your domain registrar. In this case, that's actually a different part of Route 53.
In the Route 53 console, click "Registered Domains."
Select your domain.
Choose "add/edit name servers."
Enter the correct values for the Route 53 name servers, which are the ones mentioned above, which you'll see when you click on the domain from the Hosted Zones page.
Most of this content is from my answer to a similar qestion at Server Fault.
I have a hosted zone in Amazon Route 53 service and a domain name on a registrar.
In the registrar, my DNS configurations are correctly inserted, with the four address provided by AWS when I create the hosted zone.
In the Route 53 control panel, I have the NS and SOA proper configured as it came configured when I created the hosted zone.
I also created a A Redirection : mydomain.com.br -> xxx.xxx.xxx.xxx (elastic IP)
I'm able to reach my EC2 instance with the A Record: If I type mydomain.com.br on browser it works fine.
My problem is that I'm unable to reach the CNAME's that I've created.
I have a CNAME rule: www.mydomain.com.br -> mydomain.com.br/site but when I put www.mydomain.com.br I get a DNS error on my browser.
The strangest thing is that if I consult www.mydomain.com.br on a site like https://www.whatsmydns.net it points to www.mydomain.com.br/site, which is the correct redirect. The DNS resolution aparently works fine, but I can't get it on the browser.
Any help would be nice. Thanks.
ps: I alredy tried to ipconfig/flushdns and clear chrome's cache
Try this:
Delete that CNAME record
Add an A record in Route53
Name the A record 'www' it should automatically make that www.mydomain.com.br.
Check the ALIAS-yes box
Select mydomain.com.br. from the dropdown box (note there is a PERIOD on the end)
Save and Wait about 5 minutes.
A better (and still very cheap) way to do this might be to set up a 301 redirect in an Amazon S3 bucket. Here is a link to Amazon's tutorial:
http://docs.aws.amazon.com/AmazonS3/latest/dev/how-to-page-redirect.html
Do you have a "www" A record which is pointed to your EIP?