MIAB on ec2, webhosting on S3... how?

1

I want to host email and owncloud on the miab, but web content totally separate on Amazon S3.

I understand it’s quite easy to change the A record to another IP address, but what is the correct method to point to the S3 url? Do I use a cname, one without a subdomain and the other with www. and point them both to the same url e.g. yetisoulproductions.com.s3-website-us-west-2.amazonaws.com. ??? By creating this cname, does this then automatically delete the default A records which were pointed to the miab IP address? I have a feeling I currently have conflicting records. Please advise. In AWS Route 53, you use an A record and select “alias”, see the documentation:
http://docs.aws.amazon.com/AmazonS3/latest/dev/WebsiteHosting.html

PS. Excellent software. The best I have found so far! One feature request, to make the custom DNS section more intuitive, it would be great to be able to see all of the records and modify them ourselves and if necessary, perhaps with a warning that it would void the warranty. :wink: The only other thing I can think of, would be to allow for SES outgoing mail integration with postfix and maybe also mailgun, see here:
http://docs.aws.amazon.com/ses/latest/DeveloperGuide/postfix.html

Thank you!

2

Screenshot from 2017-03-27 00-58-44.png1366×768 96 KB

As you see, I am trying to use cname to load a S3 bucket website URL for a domain yoadam.com
Yet when I go to yoadam.com , it appears to still be loading from the miab server!

3

It seems what I am trying to do is not supported by most DNS services out of the box, and I don’t think it’s fair that I had expected to do it in MIAB. There’s nothing wrong with MIAB the way it is. I learned I am trying to use “cname flattening”, something that seems to mainly be supported by Route 53 and Cloudflare, and if I need it, I should probably just use their DNS externally https://blog.cloudflare.com/introducing-cname-flattening-rfc-compliant-cnames-at-a-domains-root/

For people who require “cname flattening”, it is a possible workaround to use a www. cname, and redirect nginx to the www cname. Chances are though, that running MIAB upgrades will overwrite your nginx settings I am guessing… Have fun with that.