Route 53 supports Alias records which use Amazon S3 static websites to dynamically resolve naked domains to their www counterparts using a 301 redirect. I am wondering whether the Alias record will support SSL:

http:// example.com -> http:// www.example.com (this will work)
https:// example.com -> https:// www.example.com (will this work?)

I realize that SSL doesn't have anything to do with DNS, but Route 53's implementation of the Alias record (using an S3 static website) concerns me.

It seems like dnsimple's ALIAS record does support SSL: http://support.dnsimple.com/articles/domain-apex-heroku/

If indeed Route 53 does not support SSL and dnsimple does, how does dnsimple's implementation of the ALIAS record differ?

  • A RFC sure would be handy right about now. – Andrew B Jun 14 '14 at 2:13
up vote 1 down vote accepted

Because you will configure the S3 bucket to send a 301 redirect to www.example.com if you follow Amazon's directions, you will wind up with SSL certificate warnings if someone uses the non-www form. As far as I can tell, Amazon provides no way for you to provide your SSL certificate in this circumstance.

DNSimple has a different implementation which, instead of sending a 301 redirect, sends visitors directly to the IP address of the Heroku app (which, presumably, they look up dynamically). This works as long as Heroku is expecting it.

  • 1
    My SSL cert isn't causing problems with this redirect, but what does happen is that example.com doesn't resolve. I'm using the exact setup described in the question. Any idea how to solve this? – Uri Klar Aug 21 '14 at 8:06
  • I’m having the same problem with my https bare domain. Is there any workaround? – BM5k Jan 26 '15 at 0:13

Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

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