On Mon, Nov 28, 2016 at 3:14 PM Jason Fleetwood-Boldt
wrote:
>
> You will note that to achieve this, DNSimple reads Heroku's IP addresses *in
> real time* and updates the DNS record in real time with fixed IP
> addresses.
>
Not entirely true as there's a wedge of caching
Does Route53 support SSL at the root?
You will note that to achieve this, DNSimple reads Heroku's IP addresses in
real time and updates the DNS record in real time with fixed IP addresses.
Yes, if you don't care about SSL at the root (that is, you're ok with people
either using only
I would strongly suggest moving away from GoDaddy DNS, it causes all sorts
of issues. DNSimple seems to be the best Heroku friendly DNS provider out
there so if you can use them, then do. They support Apex aliasing along
with everything else you need to get a decent properly configured setup.
Route53 also provides this. You would use an ALIAS record pointing at the
SSL endpoint that Heroku hands you, which ultimately is an AWS elastic load
balanced instance.
On Mon, Nov 28, 2016 at 8:26 AM Jennifer Abella
wrote:
> Jason --
>
> You are the best! I really
Heroku does not provide a DNS service.
You cannot use a traditional DNS service with Heroku, as you said, because of
the non-permanent IP addresses.
For you, you have two basic options:
1. Set up a Forwarding domain on GoDaddy. (In this case you keep GoDaddy as
your primary name server--