cpanel hosting emails not working with AWS DNS servers name - amazon-web-services

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

Related

How to setup Reverse DNS in AWS Lightsail?

My domain is registered with GoDaddy. I have installed CyberPanel on AWS Lightsail server. Multiple websites are hosted successfully on same server. I am facing problem with domain email setup. I am able to receive emails but unable to send any.
Problem might be with Reverse DNS server. Don't know how to setup reverse DNS with this combination - GoDaddy, AWS Lightsail, Cyberpanel. Please Guide!
Reverse DNS Lookup
Here you can find the guide how to Configuring reverse DNS for an email server on your Amazon Lightsail instance

Nameserver update for AWS EC2 hosted website

I have deployed a simple html website running on NGINX on a AWS EC2 server. I intend to host 2-3 static websites on this server. For the time being, I have configured only 1 server block and hosted the website.
When I type the ip address/public dns name of the server in the browser, I can see my website. My domain name is registered with another service provider.
How should I update the Nameserver records in my domain registrar account? Should I just update the public ip address in the name server field or should I update the public dns name?
My domain registrar is asking for two name server details as compulsory fields. If I update the same public ip address twice, its not allowing me to save.
Please advise. I want to know the nameserver details for my EC2 based website. My website is not hosted on Amazon Route53.
Do not update your nameserver records, these are records you would use to configure where your DNS records should be resolved.
Instead you need to update/create an A record that points from the domain to your new host IP.

How to transfer email from godaddy to AWS

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

Does transferring my DNS provider from GoDaddy to AWS, where my website is hosted, affects performance of the website?

Trying to understand how routing works for a website and this question came to my mind... My Domain name is registered with GoDaddy and my website is hosted with AWS.
Does it mean request for my website are first routed to GoDaddy and then transferred to AWS? In other words, would it be more efficient for me to have my domain name registered with AWS when my website is hosted with AWS?
The request will not be routed to GoDaddy first. Only the DNS request to resolve your domain will go to GoDaddy. Once the DNS resolves it to an IP, the actual HTTP request is sent to that IP - which is your AWS instance.
Once the DNS is resolved it is usually cached (typically for 300sec) and the DNS request not sent repeatedly. So you are not gaining much by moving the domain to AWS.
Very high level flow:
Type the URL of your website in the browser
The browser tries to resolve the URL to an IP (Request sent to GoDaddy Name Servers since the domain is registered with GoDaddy)
Browser sends the HTTP request to the IP

Main domain for AWS S3 static hosting and sub domain for api

I purchased a domain from godaddy.com and I'd like to use the root domain for AWS S3 static hosting and sub domain for api.
The API server is running on an AWS EC server.
So the result should be:
- when enter mydomain.com in the browser: I should see the AWS S3 static hosting page.
- when I make a request to api.mydomain.com: all requests should be sent to AWS EC2 server.
I tried http://docs.aws.amazon.com/AmazonS3/latest/dev/website-hosting-custom-domain-walkthrough.html
As a result, the S3 hosting is working with the root domain.
But in my Godaddy domain settings page, I can't add a subdomain because the name servers are not managed by Godaddy.
Since you mention that the name servers are not managed by Godaddy, I assume that you are using AWS Route53 service. If so, that is where you should add all needed records/subdomains.
Also, by using Route53 with other AWS services, you can utilize additional benefits compared to other name service providers (ALIAS records).