- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
Some more troubleshooting is required here:
First, make sure that the DNS (Route 53) is set up correctly. From a command-line prompt, use nslookup
or dig
to ensure that the www.example.com
record is available. Even something like ping www.example.com
is fine - you want to make sure that it returns an IP address.
Second, do the same thing with example.com
.
Then, check the redirect configuration in S3 for www.example.com
.
I wouldn't suggest sharing private information in this forum; if you're still having difficulty definitely raise a ticket with the support team as they some visibility into how you've configured the services and can help from there.
Thank you for responding.
I have confirmed that ping www.example.com fails - while ping example.com is fine.
I am not certain if this means the redirect configuration should still be investigated, or does this mean the problem is definitely happening earlier such as in the Route S3 setup where I have the www.example.com hosted zone? I appreciate your clarification.
I have inquired with Tech earlier but I am on the free account so they suggested I use the forums. They pointed me to the docs for setting up S3 redirect which did work at first. It worked fine for a few days then stopped working without any changes to my AWS setup. I assumed something I did was pending and updated after a few days to break it.
Thank you. I have resolved this.
You response led me to look back at my Route S3 - realized at some point trying to get CloudFront to work I had added a second hosted zone for www.example.com. The correct solution after reviewing the docs was to have a single hosted zone example.com and add the record for www.example.com. It is now working for me.
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 3 anni fa
- AWS UFFICIALEAggiornata 4 mesi fa