AWS Route 53 Domain Name Setup | Configuring DNS with AWS Route53

AWS Route 53 Domain Name Setup | Configuring DNS with AWS Route53



This tutorial goes over setting up your domain name to point to Route 53 as well as how to create an A and CNAME record for your site! In my example I had my website purchased through godaddy but the same principles apply to anywhere you purchase a domain. It’s possible to also purchase your domain names through Route 53 as well which I would recommend but I went under the assumption most people have purchased their sites elsewhere.

Configure Route53 using Terraform Automation:

Practical Reference:
Youtube Subscription :
Facebook:
Follow blog :

#aws route 53, #awsroute53 #route53
#aws route 53 tutorial,
#aws route 53 deep dive,
#aws route 53 latency based routing,
#aws route 53 private hosted zone,
#route 53 aws,
#route 53 aws tutorial,
#route 53 domain name setup,
#route 53 aws godaddy,
#route 53 hosted zone,
#aws route 53 in hindi,
#aws route 53 tutorial in hindi

39 thoughts on “AWS Route 53 Domain Name Setup | Configuring DNS with AWS Route53

  1. Get Full Terraform Tutorial : https://www.youtube.com/playlist?list=PL_OdF9Z6GmVayanQ4cjISqY_UkrOcZtr1

  2. Bro.. mera help kardo..please
    Maine Route53 se hi liya hai Domain name and nano instance chal ra hai.. ab link nahi hopaara.. mere main koi load balancer nahi hai..

  3. Hi sir unable to perform the lab as the version of Route 53 I am getting is different than the one above. Can you kindly advice how to switch to this version of the Route 53.

  4. I am using lightsail instance and aws registered domain. when i try to send mails from workmail to gmail, Its getting received, but when tried to giv reply from gmail, its getting bounced and showing that the "because the address couldn't be found, or is unable to receive mail."

  5. This is the error I get any suggestions?
    This site can’t be reachedwww.dchrisostomo.com’s server IP address could not be found.

    Try running Windows Network Diagnostics.

    DNS_PROBE_FINISHED_NXDOMAIN

  6. After adding Route53 nameserver into DNS setting of Godaddy account, how much time it will take to working website.

  7. Hi great video explanation ..I can reach the website using Load balancer URL – but domain is still gives me and error ..

    DNS_PROBE_FINISHED_BAD_CONFIG

    can you help?

  8. How am gonna follow along when I do NOT have a godaddy account or that my domain is not hosted yet, it's only registered, I need to know how to create a damned CNAME! Like it needs to be done like yesterday.. But I can't find how to create a CNAME in AWS for G-Suite… Please help

  9. intention is good but …presentation and explanantion is totally bad very bad…hope you can improve and reupload this video…voice is bad and no clarity

  10. Really bad bad sound. Accent of present is bad enough, with terrible sound almost impossible to follow.
    Bad preparattion…. trying to create stuff, oh it is here already….

  11. u r explained domain name setup in route53 but directly open godaddy without explaining starting process in godaddy i didnt see titles like records ,name servers in godaady site whwn i opened u hav to explain full procedure in godaddy also

  12. why didnt you put A record for ezaws.xyz domain. isnt it required? you directly put alias record for elb without A record for ezaws.xyz. and what if somebody type www.ezaws.xyz ?

  13. I can buy the domain from the aws and create the record set. When i can go on test record set it will be worked properly. and when the domain enters into the browser it will generate error. In cmd it will show NXDOMAIN

  14. hey i am configuring my aws in tomcat 8080 port , i did my set up as per your video , but my load balance showing out of service, ,even if i am waiting 1 day also. can you give any suggestions.

  15. Hello, great video! Can you explain what each line of script you entered in the Advanced Details>User data box means and if they are considered values, where you would get the information? Thank you

Leave a Reply

Your email address will not be published. Required fields are marked *