Hacker News Reader

Comment by jgrahamc | Hacker News Reader

This appears to not be a problem with CloudFlare, but a problem with Dyn: https://www.dynstatus.com/. Of course, Dyn and CloudFlare have mutual customers and so if a Dyn has a problem it's possible for a mutual customer to have a problem.

View on HN

Strange, we are using CNAME apex resolution with cloudflare to point to Heroku apps, so I'm not aware that Dyn is used anywhere in that chain, but resolution is still down for those apps.

edit: resolved now.

    $ dig +short NS heroku.com    
    ns1.p19.dynect.net.
    ns4.p19.dynect.net.
    ns3.p19.dynect.net.
    ns2.p19.dynect.net.

Thanks!

Looks like your support site might need a little.. support http://i.imgur.com/X76QdaC.png

You might want to try putting it behind a CDN to cope with the load

We use Zendesk. Zendesk uses Dyn. Boom!

Reply on news.ycombinator.com