Hacker News new | ask | show | jobs
by yesimahuman 4762 days ago
Ah, got bitten by this. Just added Route 53 as redundancy, should have done that a long time ago.
2 comments
whafro 4762 days ago
Are you doing this manually? I make solid use of DNSimple's ALIAS record type, which is also supported by Route 53, but DNSimple says they don't support AXFRs (http://support.dnsimple.com/articles/master-slave-support).
link
yesimahuman 4762 days ago
Honestly, I'm not a DNS pro, but I added more nameservers in our registrar to point to R53 nameservers, then setup R53 to point to our Heroku app w/ alias support by following this guide: https://devcenter.heroku.com/articles/route-53
link
nate 4762 days ago
Are you using route53 to do an alias AND have the root domain use SSL? The setup at route53 is confounding me. I thought I'd setup a CNAME www.domain.com that points to sub.herokussl.com, and than an A record Alias that points domain.com to www.domain.com. But Amazon seems to not avow that the CNAME record is a "Record Set" that I can use for this.
link
whafro 4762 days ago
That's interesting. Have you tried it the other way around?

- domain.com ALIAS sub.herokussl.com - www.domain.com CNAME domain.com

link
nate 4762 days ago
Amazon doesn't like that Alias either. A friend on mine, Scott, just figured out though that you can point your Alias record at any ELB even outside your account:

https://twitter.com/scottvdp/status/341604885600534530

So I can make an Alias record to the ELB that heroku is pointing at with their SSL CNAMES.

link
yesimahuman 4762 days ago
Did you set up the S3 bucket with static file hosting redirecting to the www subdomain, before you try adding the alias in 53?
link