- Newest
- Most votes
- Most comments
I found that the targets for my alias records were wrong, so I fixed those. However, it's still not working.
I also found the troubleshooting guide here:
https://aws.amazon.com/premiumsupport/knowledge-center/route-53-dns-website-unreachable/
and followed it to here:
https://aws.amazon.com/premiumsupport/knowledge-center/route-53-reachable-resource-record-sets/
I don't have an MX record at the moment (which is fine), but digwebinterface.com returns the following:
preed.us. 899 IN SOA ns-1332.awsdns-38.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
which looks to me like it's making it to AWS, so I don't understand why it won't forward to my Elastic Beanstalk site.
Looks like the problem was that I'd put https:// in the alias records and it had gotten munged into some weird encoding with a lot of backslashes. Could have sworn I tried both with and without that, but anyway removing it seems to have fixed things.
I'd still appreciate any pointers to troubleshooting materials.
Relevant content
- "This site can’t be reached " -> Using Lightsail with a wordpress instance and a Route53 Domain NameAccepted Answerasked a year ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago