Hacker News Reader

exitnode_ttl0on Issues with upstream DNS provider

I went back to the CNAME now and everything is up and running. Fingers crossed that Heroku reports to have the issues resolved.

exitnode_ttl0on Issues with upstream DNS provider

Good points, thanks!

exitnode_ttl0on Issues with upstream DNS provider

I am now seeing one of my services coming back online. For this service I have not replaced the CNAME. Anyone else seeing some service restoration as well?

exitnode_ttl0on Issues with upstream DNS provider

This is essentially doing the same thing right? What is the advantage of this method? Less DNS changes?

(not trying to be snarky, trying to understand)

exitnode_ttl0on Issues with upstream DNS provider

There is one more problem I can think of (but yes you're right, it can't get worse than 'total outage'): Heroku might detect that the CNAME is missing and will deactivate some stuff from their automatic domain management / TLS certificate issuing.

exitnode_ttl0on Issues with upstream DNS provider

Anybody know what the risks are for doing this? We have not one but 13 heroku domains running where we might do this.

What are the chances that their current work on the DNS issues might replace the underlying IP-addresses and hence we are making it harder on ourselves?