I have purchased a domain in aws route 53 and created a business mail from godaddy. After creating mail in godaddy, it is prividing me some recordsets such as MX record, cname record etc. I have added these records in AWS route 53 hosted zone. But still not getting to activate my mail. Anyone Please help me to fix it out.
You need to add the NS records for your domain as your authoritative DNS server at the domain registrar (where you purchased your domain from)
Related
I have a scenario that gives me headache for a while now. I bought a domain on Namecheap, hosting on Godaddy cpanel, but later decided to host on Aws ec2 instance, but I don't want to use the SES service from Amazon. Now that was successful.On trying to setup the email account on the Godaddy cpanel, I can only send emails , but not receive. I tried several mx record settings, but none worked.
Domain from Namecheap --- works
Email service - Godaddy Cpanel email -- can only send, no receipts.
Website hosting - Aws ec2 ----works
I would like to know the correct setup for this. Any help would be appreciated.
What is that you are trying to host on EC2? Is it an application?
Where is your Email Hosting done? Is it in GoDaddy?
In order to do that you have to change your MX Record entries in your DNS.
You have to add the MX entry provided by the cpanel for that particular domain in your dns to get your incoming emails service working.
You are able to send emails because there is no need of MX when you are sending mails. You are using SMTP for sending mails out from your server.
Your website should be working if you have added your amazon ec2 instance public ip in your DNS.
You can make things simpler by moving your dns to cpanel i.e. on godaddy server by changing nameservers in your name cheap panel which is given by godaddy guys. You then have to add A record which must be pointing to your AWS ec2 instance public IP and your MX must be set bydefault in your cpanel server.
My client is currently hosting his site on a shared GoDaddy hosting plan, an also his emails accounts. Question is... how can I migrate his website to Digital Ocean and keep the emails on GoDaddy?
I had an recently where I could not receive emails on my goDaddy account once I have moved the nameservers to DO. For anyone facing this issue, the below steps should fix it.
To migrate hosting from goDaddy to DO, follow the below link
https://www.digitalocean.com/community/tutorials/how-to-point-to-digitalocean-nameservers-from-common-domain-registrars
Once you have pointed nameserves, your traffic will be redirected to DO. Now if you want to use the email service provided by goDaddy, you will need to point your DO "MX" records back to godaddy.
First you will need to know the goDaddy incoming email server details. To obtain this, you will need to go to email server settings within your goDaddy Dashboard. The server details will look something like
Incoming server (IMAP):
imap.secureserver.net
Incoming server (POP3):
pop.secureserver.net
You will then need to add these details as MX Records in your Digital ocean domain DNS settings page. DO will then route emails to your goDaddy email service.
These details will take time to reflect. For me it took a day to start receiving emails on goDaddy.
Hope this helps!
Yes, you could just change your zone records to reflect what you want to do. Presumably you want to transfer the DNS zone to Digital Ocean and only keep the email at Godaddy.
In Godaddy's domain name manager you can change over to the Digital Ocean name servers.
ns1.digitalocean.com
ns2.digitalocean.com
ns3.digitalocean.com
Check things out:
dig ns example.com
and
whois example.com
The name servers should be the above DO name servers.
The only thing you need to point back at Godaddy will be Goddady's MX records. unless, of course, you're using Office 365 email, which a lot of Godaddy's customers seem to use, in which case lookup the appropriate MX records for Office 365.
I hope this helps.
This is possible, recently I did the same with Hostgator and GCP ( Mail service from webmail and app in Google Cloud ). These are the steps I followed.
1) Add new A record ( if possible/allowed add with name # ) in your
shared/hosting/cpanel service, and point it to your cloud providers
IP(the IP on which your app is running).
2) Add another A record with name www and point it to the IP of your
service running in the cloud.
3) Delete the CNAME record called mail.
4)Add new A record with name mail and point it to your cpanel /
webmail service providers IP.
5)Add MX record and point it to destination mail.yoursitename.tld and
set the priority as 0
By this point, you will be able to send mail.
6) Add SPF record ( TXT record ) or go to Authentication settings in
the Email section in your cpanel and enable SPF.
7)Go to Email Routing in the Email section in your cpanel and select
your domain then choose Local Mail Exchanger under Configure Email
Routing. That's it now you will be able to receive emails also.
Link to my original answer
I am developing a web site and I have it hosted in AWS. To access it I have a domain domain.org and I use this domain with a sub-domain for a web service.
So I have
CName
my.domain.org CNAME mywebsite.amazonaws.net
and it works perfectly.
The problem now is that I'm trying to use the same sub-domain as a email service with mailgun. Hence I want to be capable to have something like example#my.domain.org. Mailgun tells me to set this configuration:
TXT
my.domain.org TXT v=spf1 include:mailgun.org ~all
mailo._domainkey.my.domain.org TXT k=rsa; p=SOMEPASSWORDNUMBERS
MX
MX 10 mxa.mailgun.org
MX 10 mxb.mailgun.org
CNAME
email.my.domain.org CNAME mailgun.org
I have done all this with my DNS provider, but the status of the domain in mailgun is still unverified, specifically the TXT record my.domain.org TXT v=spf1 include:mailgun.org ~all cannot be checked.
I have made some research and found that I should include an A Record with the sub-domain and the IP address that points to the mailserver in mailgun, example:
A Record
my.domain.org A nnn.nnn.nnn.nnn:
but my DNS provider DOES NOT let me do it, and it says CNAME record already exists for the entered Host name
I'm struggling to fix this, but I am still stuck. And I haven't found someone with the same problem on the internet who has solved it already, what I want to know is, if is it possible to use a sub-domain for a web page service using a CName, and as well for a email service?
Many DNS providers don't allow this, please create a new zone for the particular subdomain and it should work.
I would like to ask if its possible to retain the email of my domain to godaddy and is hosted in gmail but the hosting is in different provider like namecheap. I know how to point the nameserver of namecheap to godaddy but my problem is with the email
Assuming I understand correctly, you are using Google Apps For Mail. If so, you may simply host your domain name with Namecheap and then set up Google MX records for your domain name. This way you will have your domain hosted with Namecheap and mail service handled by Gmail. No need to include GoDaddy into this chain.
You may find MX records here: https://support.google.com/a/answer/33915?hl=en
These MX records should be set up in your cPanel (if you have a hosting plan) or at the Advanced DNS page of your Namecheap account (if you are using Namecheap's Premium or Basic DNS).
We have a client with a website hosted on AWS and he is using Google apps to send notification emails. These emails are marked as spam/junk.
We have set an SPF record as per Google's documentation. Clicking on view messege source I found SPF:softfail. From what I understand, setting up reverse DNS/PTR record can also help, but we have 2 production instances behind an ELB and we're not sure how to set that up as it doesn't have a public IP.
This is how our Route53 setup looks:
example.com A ALIAS ***.elb.amazonaws.com.
example.com MX 1 ASPMX.L.GOOGLE.COM.
example.com TXT "v=spf1 include:_spf.google.com ~all"
mail.example.com CNAME ghs.googlehosted.com
Apparently, the client was sending all of his emails through local smtp without using Google Apps. I've added his IP to the SPF record temporarily until he moves the emails over to go through google. We have also set a DKIM record.
PTR records and ELBs had nothing to do with it.