How to transfer email from godaddy to AWS - amazon-web-services

Here's my scenario:
I bought a domain from goddady
I set up email on godaddy as an addon
I hosted a web application on AWS
In order to secure my API calls I needed to transfer my domain from godaddy to AWS (I should have bought the domain on AWS to begin with but I didn't know I could do that)
I have successfully transferred my domain
Now my email (obviously) doesn't work anymore.
My question is: do I have to transfer email over to AWS as well, or is there just some setting that I will have to change on godaddy to point to AWS now? Is there a similar service on AWS (hosted email) that I can use?

As you have moved the domain into AWS, you need to move/create the MX(Mail exchange) records in route 53 too. Just create an MX record type entry in route 53 with name as your domain name and values with the list of mail servers that you can grab from godaddy. Here is the link to find how you can get the mail records form godaddy
https://au.godaddy.com/help/checking-and-managing-my-mx-records-7590
For more information about how to add MX records. follow this link
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/ResourceRecordTypes.html#MXFormat

Related

cpanel hosting emails not working with AWS DNS servers name

info: i have two hosting server one is on skyhost.com and the other is on AWS Lightsail. skyhost is a cpanel hosting where i register my domain name and my emails accounts. My website is hosted on AWS Lightsail with the domain. my website is contain the domain which is register on skyhost. The website is working fine because AWS DNS are propagated with domain which is register on skyhost.
Issue: But the email info#mycompany.com are not working (sending or receiving). I am not able to login the accounts since i host my website on AWS because i don't understand how can i add DNS records in Lightsail AWS of skyhost for mail exchange or something else...
example: (65.91.30.99) that is the ip of cpnel skyhost. staticip-1 that is a AWS server ip
To keep it simple, the MX records do not point to IPs.
You will need to set the sub-domain to the naked domain example.com or "#" in some cases. (I have not used the light sail DNS console before)
But you then set up the "Maps to" as mail.example.com and then create an A record for mail.example.com to point to 65.91.30.99
This is how basic DNS routing works for email.
More info here: https://lightsail.aws.amazon.com/ls/docs/en_us/articles/lightsail-how-to-create-dns-entry

Can't add google Dns confirmation Txt Record to godaddy's name server

I am trying to verify my website on google console and it is asking me to add the verification code into dns configurations. I purchased the domain from godaddy and hosting my website on aws server that's why godaddy's dns configuration has name servers provided by aws.
Now when I am trying edit the records of my domain in Godaddy.
It says:
We can't display your DNS information because your nameservers aren't managed by us.
Which is because I am not using Godaddy's nameservers.
I wanted to know which is the right place to add the googe verifcation code is it godaddy or aws?
If it is AWS where should I add the record.
Open AWS Route53
Create Hosted Zone if you are not created.
If already created then create record set
Select TXT record and add your value.

How to got verify DNS record in Godaddy# by Amazon Web Service#?

I want to send email using AWS Simple Email Service from my domain email address, but during configuration, finding verification issue by AWS.
1) I have purchase domain from GoDaddy and create email with that domain.
2) Register my domain in AWS portal.
2) To enable email serviice, AWS provided me TXT and CNAME record, which were supposed to be set in DNS record in GoDaddy Portal. I hhave done that setup.
3) AWS supposed to verify those record fron DNS setting but it is not able to verify.
Please help, Thanks in Advance :)
Just for better visibility, #michael-sqlbot's answer is working.
If you have put-this-into-host.your-domain.com then just use put-this-into-host, because the domain will automatically be suffixed.

Cannot send or receive any emails by using Cpanel after I updated the nameserver to amazon Route 53

I registed the domain name in WHC website and changed the namesever of the domain to the nameserver that generated by Amazon router 53.
The domain is online now but i cannot receive or send any emails by using Cpanel.
someone suggested me to use Amazon SES service to fix this problem.
I associated the SES to my domain and route 53, and added new TXT and CNAME records to the Cpanel setting. but the problem still there.

How to move a domain from Godaddy to AWS Route 53

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.