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 have registered the domain duhastdiewahl.org at Amazon AWS Route 53.
I do it step for step like this:
http://share.pho.to/AAUSM
Create Hosted Zone (NS/SOA-Record default)
Add A-Record to my elastic ip adress for my EC2-Instance
Unfortunately if i ping the adress the name can't be resolved and tools like http://mxtoolbox.com says that the nameservers couldn't be found.
Can anybody tell me what is wrong?
Thank you for your support :)
Your nameservers are configured incorrectly in Route 53 "Registered Domains" -- they don't match the servers assigned to you in "Hosted Zones."
Route 53 is two different services -- domain registration and DNS hosting -- and the settings between the two of them need to match. One possible cause of a mismatch is deleting and recreating your hosted zone. That wouldn't fix anything, but a lot of people seem to try it anyway. When you do that, it assigns four new name servers do your domain for hosting -- but the registrar service doesn't learn about this, because there's not necessarily a connection between the two services. You could register a domain on one AWS account, and host the DNS on another, if you wanted -- the two "sides" of Route 53 are essentially independent.
To fix:
In the Route 53 console, click Hosted Zones, click your domain, and make a note of the assigned 4 name servers. Don't change anything here.
Click "Registered Domains."
Select your domain.
Choose "add/edit name servers."
Enter the correct values for the assigned Route 53 name servers, which you obtained from the Hosted Zones screen.
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?
Since Godaddy went down for some hours my client and I are very upset and want to change everything to AWS.
Everything is done so far, only the domains (blablabla.com) are missing, I'm having a hard time trying to migrate from godaddy to Route 53, Do I have to remove from one and create from scratch from AWS?
Does anyone have any experience on how to do this?
the solution:
Login on your aws console;
Click on Route 53;
Create Hosted Zone;
Select your new created host title and click "Go to Record Sets", take note of the nameservers;
Login on your Godaddy account;
Select your domain;
Go to Nameservers and click SetNameservers;
paste all the four you took from "Go to Record Sets" Route 53;
and that's it..., you don't have to rely on this horrible service Godaddy provides anymore
You can transfer the domain registration to AWS Route 53.
You have to "unlock" the account.
Log On to Go Daddy.
Go to Domain Details Then Settings:
Lock: Set to Off
Authorization Code: Email My Code
Route 53 will need the authorization code to complete the transfer request.
Here are the steps to migrate your internet domain name to AWS route 53 (DNS Manager).
** Be careful where your mail server is hosted, either in the Godaddy mail service, Gmail (gsuite) or in your Cpanel server (VPS/Server).
** To empower your Domain DNS capabilities, you need to transfer the name servers, DNS records and domain name to AWS route53, thats why it's recommended to move to AWS Route 53. You can keep Godaddy to be owner of your yourdomain.com and manage your DNS by Route 53
STEPS:
Go to Godaddy DNS records and understand each of them and note them (Take a screenshot)
Go to AWS route 53, Crete a Public hosted Zone (Create your domain on AWS route 53). Here is a good tutorial about it:
https://www.clickittech.com/aws/migrate-godaddy-to-aws-route53/
Copy your Godaddy DNs records into your Public hosted zone previously created. Remember, each record needs to exist in the new aws zone.
Change your Name Servers to AWS Route 53. What does it means? In order to allow AWS route 53 to manage your domain, DNs records, etc. you need to change your actual Godadaddy Name server (NS) Records to AWS Records.
Go to Godaddy admin Panel and Login
Go to DNS Management
Under Name Servers Click on Change - > Custom - > Change Name Servers
You need to change from NSx.domaincontrol.com to the AWS Name servers.
More info: https://www.clickittech.com/aws/migrate-godaddy-to-aws-route53/
After 4-8 hours your Name Servers will be reflected and propagated around your country, world and networks.
Practically you are done with this.
Additionally, if you need to migrate your website or web app to AWS go to this tutorial, great explanation, see below:
https://www.clickittech.com/aws-migration/transfer-domain-aws-migrate-move-website-aws/
The answer from The Poet above is good for moving everything, but it will also kill your email service with GoDaddy. If you want to keep the email servers running at GoDaddy, you will also need to get your MX email servers and their priority numbers. Mine looked like this...
0 smtp.secureserver.net
10 mailstore1.secureserver.net
Take these over to your Route53 settings, click Create Record Set, choose a type of MX Mail Exchange, and paste these values in (with the number in the front as shown above). Save the record set.
Also PJT was correct; all domain info in Route53 ends with an extra period for some reason specific to AWS, but don't worry about it--it doesn't affect production behavior. When you copy your four from Route53 to paste in GoDaddy's Name Servers, you will need to do them one at a time and trim off the extra period at the end.
If you want to migrate your DNS records to Route 53, you'll need to export them from GoDaddy and recreate them manually in Route 53.
To do this in one automated step, consider a DNS migration tool such as DNSTools.ninja, as outlined here: https://dnstools.ninja/migrate-bind-aws-route53-safely-3-commands/
Be careful with google mx records if you have them.
Why switch to route 53?
AWS Route 53 doesn’t limit you to 64 subdomain.
AWS allows you to host buckets with route 53
It all comes at a 50 cent/month.
AWS Nameservers
Now to answer your question, you need move the name servers to route 53. That means in godaddy name server section should be filled with aws name servers.
See the steps here.
https://metamug.com/article/dns-migrate-godaddy-to-route-53.php
The detailed steps to transfer the domain registrar from GoDaddy to Route 53 is given at https://cloudopian.com/blog/how-to-transfer-domain-registrar-from-godaddy-to-amazon-route-53/
Remember, you first need to transfer your name servers by creating a hosted zone in Route 53 and pointing your godaddy hosted domain to use Route 53's name servers instead of it's own name servers.