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
Related
I have a Wix website and in order to connect my AWS domain to it so
I changed the Nameservers (in registered domains to Wix)
Updated the NS records (in hosted zones to Wix)
*I noticed (when in hosted zones) that when I click "Hosted Zone Details" it has AWS Name servers.
I have WorkMail set up but now it won't find the correct settings (after it was previously working well) and it has the message: "Your Route 53 hosted zone for this domain needs to be set as authoritative. To learn how to set a hosted zone as authoritative, see Migrating DNS in the AWS Route 53 Developer Guide."
So, I'm not sure what to do in order to make my domain work with Wix and have my Workmail working correctly. It seems like one or the other unless I'm missing something, any help is appreciated!
Your right, you need to pick one. I dont believe there is a requirement for either of them where your namesevers are hosted - its just they point you towards their own services as its generally easier to setup ;-)
Your old zone in Route 53 will have MX, TXT and CNAME records specifically for workmail. When you switched nameservers you lost those records. Take a look at this page for more info: https://aws.amazon.com/premiumsupport/knowledge-center/add-verify-domain-workmail/
Option 1
Leave your nameservers pointing to WIX and re-setup WorkMail
Option 2
Revert your name servers to Route53 and setup WIX to use route53 (im not familar with Wix but this looks about right - https://support.wix.com/en/article/connecting-a-domain-to-wix-using-the-pointing-method - basically you create an A record for example.com and a CNAME for www.example.com in Route53 with values from Wix.
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).
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.
We purchased a domain from GoDaddy, for example, say mycompany.com.
My colleague then moved it to Wix.com to publish our marketing site, which will be available at the mycompany.com url. I need to add a subdomain in AWS, pointing to a Cloudfront CDN endpoint.
To shed more light into the current situation, here is a little more info:
When I check GoDaddy, it shows Nameservers, referencing the Wix servers. For DNS, it says We can't display your DNS information because your Nameservers aren't managed by us.
When I check Wix.com, I see that Managed by Third Party, Connected by DNS and still provides the option to transfer to Wix.
Both Godaddy and Wix provide the option to add a subdomain.
I'd rather do that in AWS.
What is my best option here? Should I transfer the domain to AWS and manage it there? If so, how do I then route traffic from mycompany.com to the marketing site?
Is there a way to keep it as is, but still add a subdomain on the AWS side for example.mycompany.com?
I really regret not registering this domain via AWS in the first place, but lesson learned. Any help would be much appreciated.
I am assuming that your DNS is being hosted via wix.com.
If you want to migrate to Route 53 its not actually too hard. Start by setting up a public hosted zone within Route 53 with the domain name you setup.
Next you would want to perform a zone lookup for all your DNS records, you can use Googles DIG Tool with the ANY option or do this via cli by running dig example.com ANY.
Now that you have all the records you will need to create them within your public hosted zone, follow this tutorial if you need any assistance. Do not add the SOA or NS records.
Now that all records have been migrated get the values from the NS record in your public hosted zone and replace the nameservers within GoDaddy to point at these values.
Your DNS will migrate over whichever period the TTL of your previous NS record is set as. Once this has migrated and it working you can add your CNAME record as you originally wanted to add.
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?