Ce site est optimisé pour être consulté depuis un navigateur moderne dans lequel JavaScript est activé.

Pourquoi Heroku déconseille-t-il les noms de domaine « nus »?

ayi

I ran across <a href="https://devcenter.heroku.com/articles/avoiding-naked-domains-dns-arecords" rel="noopener nofollow ugc">this page</a> in the Heroku docs…
<blockquote></blockquote>
Naked domains, also called bare or apex domains, are configured in DNS via A-records and have serious availability implications when used in highly available environments such as massive on-premise datacenters, cloud infrastructure services, and platforms like Heroku.
For maximum scalability and resiliency applications should avoid naked domains and instead rely solely on subdomain-based hostnames.
Does anyone here speak Enterprise? What are the “availability implications” they’re warning about?
(I notice that <a href="http://stackoverflow.com" rel="noopener nofollow ugc">http://stackoverflow.com</a> works no problem, so evidently there are viable alternate philosophies on this issue.)
<hr>
Source : <a href="https://devcenter.heroku.com/articles/avoiding-naked-domains-dns-arecords" rel="noopener nofollow ugc"></a>

ayi_2

What they’re talking about is that when you use a <code>CNAME</code> to point to their services (which is only possible on subdomain, not the zone root - it can’t coexist with the <code>SOA</code> and <code>NS</code> records that are required on the root of your zone), they can make a change to their own DNS records to work around some kind of availability issue.
With a zone root, you must use an <code>A</code> record to point to a specific IP address for the service. If they have an issue with routing, or some kind of denial of service against that specific address, they’re not able to update your zone’s <code>A</code> record to point to a different IP on the fly; they can update their own, though, and that’s what a <code>CNAME</code> allows them to do.
This doesn’t apply to Stack Exchange because they aren’t using a third party’s platform; they’ll be the ones responding to an availability issue, so whether it’s a <code>CNAME</code> or an <code>A</code> makes no difference to them.