AWS Route53 GoDaddy Issues?
Your thoughts?
Yes, I have had issues with this when using BeanStalk.
I had a bunch of DNS records defined on the GoDaddy side including some forwarding rules etc.
I noticed that the root domain wasn't forwarding to www and was unreachable! This was evident when my Google AdSense ads.txt file wasn't being picked up / recognized by the crawlers.
I was able to solve the issue by creating the host zone on AWS side and then listing those DNS name servers as the custom name servers on GoDaddy side (didn't use GoDaddy default name servers).
Use the AWS Route53 "Hosted Zone" feature to create your CNAME records, etc. in AWS itself. Then you can simply reference these NS host names in GoDaddy and do all record config in AWS.
GoDaddy is not my friend :(
GoDaddy is not my friend :(
just point everything to AWS ... don't use GoDaddy to configure your DNS settings if you are hosting your application in Elastic Beanstalk!