Log in to your Amazon Web Services Account. In AWS Management Console, find or Search Route 53, and at DNS management-click the hosted zones. In my video, there are two hosted zones already, considering I already have two websites here.
To continue the process click the “Hosted Zones”. If you want to add settings to your website, you may click the website name to modify them. In our case, we will add a new domain. Just click the Create Hosted Zone, then at the domain name, type your website name. In my case pcingredient.com, “comment” is optional, and “Type ” is “Public Hosted Zone” and click create.
Then go back to your EC2 instance to get the information about your website. Copy the following details “Public DNS (IPv4) and IPv4 Public IP.” You will need this information for your DNS Configuration.
Go back to Route 53 and add the public DNS (IPv4) and IPv4 Public IP information. In the create record set and in the following information set, name: “www”, Type: “A-IPv4 address”, Alias: “No”, TTL(seconds): default value, Value = “your IPv4 Public IP” then click create.
Create a record set once again, and then I add the second information. See the video at 02:21. Once this configuration is finished, you are already done configuring your domain name to access your website instead of your IP address.
What if your domain name comes from another hosting provider
To configure it, go to your hosting provider website and modify the dns settings to access the AWS DNS. I bought the domain from another hosting provider on my website, so I need to login to their dashboard and configure my domain to access the AWS DNS.
Once login into your hosting provider. Goto to your domain name, open it, and find the manage name servers. Use custom nameservers and change it with this AWS DNS.
It takes two days before the changes will take effect. At this time, your website is unavailable.
DNS record types do Amazon Route 53 support
Amazon Route 53 currently supports the following DNS record types:
A (address record)
AAAA (IPv6 address record)
CNAME (canonical name record)
CAA (certification authority authorization)
MX (mail exchange record)
NAPTR (name authority pointer record)
NS (name server record)
PTR (pointer record)
SOA (start of authority record)
SPF (sender policy framework)
SRV (service locator)
TXT (text record)
Amazon Route 53 also offers alias records, which are an Amazon Route 53-specific extension to DNS. You can create alias records to route traffic to selected AWS resources, including Amazon Elastic Load Balancing load balancers, Amazon CloudFront distributions, AWS Elastic Beanstalk environments, API Gateways, VPC interface endpoints, and Amazon S3 buckets that are configured as websites. Alias record typically have a type of A or AAAA, but they work like a CNAME record. Using an alias record, you can map your record name (example.com) to the DNS name for an AWS resource(elb1234.elb.amazonaws.com). Resolvers see the A or AAAA record and the IP address of the AWS resource.
On this website, I only configure those settings. But for the other website, I use MX record to access my AWS Workmail account to set up an email account, and this is the settings
MX Simple – No 10 inbound-smtp.us-east-1.amazonaws.com