1

I had purchased the domain on goDaddy a while back and now I am trying to setup an S3 static website.

I followed the instructions on setting the website from AWS manual

I followed the instructions on setting my route 53 migration from AWS manual

My Mail Exchange was having an issue after the switchover. So I used the default servers from GoDaddy on the route 53 record sets and that seems to be working.

but my site has not propagated yet and it still shows blank page.

EDIT: I am not getting any errors. It's just a blank page with

<!DOCTYPE html><body style="padding:0; margin:0;"><html><body><iframe src="http://mcc.godaddy.com/park/ZGt0YwR2BP4lZwRhZmLh" style="visibility: visible;height: 100%; position:absolute" allowtransparency="true" marginheight="0" marginwidth="0" frameborder="0" width="100%"></iframe></body></html> Also, it has been close to a week now since I have changed the settings

EDIT2: http://bucketname.s3.amazonaws.com works for me. So the issue is with the DNS and that's what I can't figure out.

Improve this question
7
  • 1
    Are you receiving a server error (e.g., 5XX), or a timeout while connecting? I'd suggest running a traceroute to see where you're ending up at. Try using some of the online tools here. Also, it's helpful to know how long it's been. Normally if your MX is already resolving, your web server should be as well (so I'm suspecting there's a server configuration error at play).
    – dan ♦
    Commented Jul 18, 2017 at 5:11
  • Is the IP address reported that of your S3 bucket? Are the name servers (NS records) pointing to amazon servers? Also if you add an entry in your /etc/hosts (or hosts.txt file on Win) like xxx.xxx.xxx.xxx example.com www.example.com using your domain name and your S3 bucket IP, does the website then work on that computer?
    – Stephen Ostermiller ♦
    Commented Jul 18, 2017 at 18:31
  • @StephenOstermiller I am sorry for my ignorance but I am very new at this. As far as my understanding of the S3 user manuals suggest, the S3 buckets don't have static IPs. The IP in the A record shows on the dig report. the Name Servers from the route53 also show up on that
    – g0rd
    Commented Jul 18, 2017 at 20:21
  • 1
    Can you post your actual domain name? Also add screenshots of how you configured your NS records at the registry and how you set up records in Route 53.
    – Stephen Ostermiller ♦
    Commented Jul 19, 2017 at 9:38
  • 1
    184.168.221.36 is GoDaddy's domain parking server. You are using Route 53 to point to the wrong thing. gabehou is correct in his answer, you need to use alias records to point to bucketname.s3.amazonaws.com. (Since you have email set up, a CNAME record at the apex would break mail, so use ALIAS records instead.)
    – Stephen Ostermiller ♦
    Commented Jul 19, 2017 at 16:22

1 Answer 1

Reset to default
1

Your DNS records are not configured correctly. There are A records that are still pointing to a different location while the CNAME is pointing to your Bucket. Remove you CNAME that is pointing to the buckets and edit the A records make sure to set yes to ALIAS and remove the wildcard A record the one with the *

You should only have 2 A records and both should be set yes to ALIAS

www.example.com A ALIAS s3-website-us-east-1.amazonaws.com

example.com A ALIAS s3-website-us-east-1.amazonaws.com

Improve this answer
0

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.