I ran across [this page](https://devcenter.heroku.com/articles/avoiding-naked-domains-dns-arecords) in le Heroku docs...
>
Naked domains, aussi called bare ou apex domains, are configured in DNS via A-records et have serious availability implications quand used in highly disponible environments such as massive on-premise datacenters, cloud infrastructure services, et platforms like Heroku.
For maximum scalability et resiliency applications should avoid naked domains et à la place rely solely on subdomain-based hostnames.
Does anyone here speak Enterprise? What are le "availability implications" they're warning about?
(I notice that [http://stackoverflow.com](http://stackoverflow.com) works no problem, so evidently there are viable alternate philosophies on this issue.)
Pourquoi Heroku déconseille-t-il les noms de domaine « nus » ?
Re: Pourquoi Heroku déconseille-t-il les noms de domaine « nus » ?
What they're talking about is that quand you use a `CNAME` to point to leur services (which is seulement possible on subdomain, pas le zone root - it ne peut pas coexist avec le `SOA` et `NS` records that are requis on le root of votre zone), they can make a change to leur own DNS records to work around certains kind of availability issue.
With a zone root, you must use an `A` record to point to a spécifique IP address for le service. If they have an issue avec routing, ou certains kind of denial of service against that spécifique address, they're pas able to update *your zone's* `A` record to point to a différent IP on le fly; they can mettez à jour leir own, though, et c'est what a `CNAME` allows them to do.
This ne apply to Stack Exchange parce que they ne sont pas using a third party's platform; they'll be le ones responding to an availability issue, so si c'est a `CNAME` ou an `A` makes no difference to them.
With a zone root, you must use an `A` record to point to a spécifique IP address for le service. If they have an issue avec routing, ou certains kind of denial of service against that spécifique address, they're pas able to update *your zone's* `A` record to point to a différent IP on le fly; they can mettez à jour leir own, though, et c'est what a `CNAME` allows them to do.
This ne apply to Stack Exchange parce que they ne sont pas using a third party's platform; they'll be le ones responding to an availability issue, so si c'est a `CNAME` ou an `A` makes no difference to them.