Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Issues with upstream DNS provider

status.heroku.com

Post reply on HN
Print view View original

41–50 of 159 posts

Re: Issues with upstream DNS provider

#42

Post by mhale »

This does not appear to be a total outage. I cannot reach any of our sites, and Pingdom also reports we are down, however, I can see normal looking traffic reaching our servers (via heroku logs --tail). In addition, members of our team are reporting via Slack that some can reach our Heroku-hosted sites, others cannot. It seems to be ISP-related. Two people within 1 block of each other on different ISPs see different results.

We proxy some services through Cloudflare to gain IPv6 support, and all of those are down, which suggests the Cloudflare -> Heroku network route is broken.

Re: Issues with upstream DNS provider

#43

Post by mtlynch »

bobsingor wrote: post #30
rajamaka wrote: post #9

Production completely inaccessible, on the plus side I might finally now get backing to migrate away from the Heroku cesspit.

Yes, i'm also done with Heroku. What alternative do you recommend?

Left Heroku for Fly.io a year or so ago and have been very happy.

Re: Issues with upstream DNS provider

#44

Post by bfirsh »

rsweeney21 wrote: post #35

We just deployed a workaround that brought our site back up. 1. Find your DNS Target in heroku. It should end with .herokudns.com 2. Lookup the historical DNS record to get the IP addresses. You can find historical DNS records here: https://securitytrails.com/dns-trails 3. Replace your CNAME record in your DNS provider with A records that point to the IP addresses you just found. Your site should come back up shortly…

This got us back online. Thank you so much.

Re: Issues with upstream DNS provider

#45

Post by theunixbeard »

rsweeney21 wrote: post #35

We just deployed a workaround that brought our site back up. 1. Find your DNS Target in heroku. It should end with .herokudns.com 2. Lookup the historical DNS record to get the IP addresses. You can find historical DNS records here: https://securitytrails.com/dns-trails 3. Replace your CNAME record in your DNS provider with A records that point to the IP addresses you just found. Your site should come back up shortly…

Presumably if your site is behind Cloudflare then this strategy won't work, right? Since the IP addresses that Security Trails sees are just of Cloudflare rather than your actual Heroku IPs...?

Or is it possible in the Cloudflare dashboard there is somewhere to see your Heroku server's IP address?

Re: Issues with upstream DNS provider

#46

Post by bfirsh »

theunixbeard wrote: post #45
rsweeney21 wrote: post #35

We just deployed a workaround that brought our site back up. 1. Find your DNS Target in heroku. It should end with .herokudns.com 2. Lookup the historical DNS record to get the IP addresses. You can find historical DNS records here: https://securitytrails.com/dns-trails 3. Replace your CNAME record in your DNS provider with A records that point to the IP addresses you just found. Your site should come back up shortly…

Presumably if your site is behind Cloudflare then this strategy won't work, right? Since the IP addresses that Security Trails sees are just of Cloudflare rather than your actual Heroku IPs...? Or is it possible in the Cloudflare dashboard there is somewhere to see your Heroku server's IP address?

You need to put in the herokudns.com address that the CNAME is pointing at – e.g. stark-wisteria-rnbgkawldfk6gq7m8308ytts.herokudns.com in our case.

Re: Issues with upstream DNS provider

#47

Post by [deleted] »

rsweeney21 wrote: post #35

We just deployed a workaround that brought our site back up. 1. Find your DNS Target in heroku. It should end with .herokudns.com 2. Lookup the historical DNS record to get the IP addresses. You can find historical DNS records here: https://securitytrails.com/dns-trails 3. Replace your CNAME record in your DNS provider with A records that point to the IP addresses you just found. Your site should come back up shortly…

[deleted]

Re: Issues with upstream DNS provider

#48

Post by ______ »

rsweeney21 wrote: post #35

We just deployed a workaround that brought our site back up. 1. Find your DNS Target in heroku. It should end with .herokudns.com 2. Lookup the historical DNS record to get the IP addresses. You can find historical DNS records here: https://securitytrails.com/dns-trails 3. Replace your CNAME record in your DNS provider with A records that point to the IP addresses you just found. Your site should come back up shortly…

Bless you! Thank you for taking the time out of your day to help us internet people :)

Re: Issues with upstream DNS provider

#49

Post by ab-dm »

SamHoustonCM wrote: post #41

Why does Heroku have so many uptime issues? Seems to be happening every few months. Last week there was downtime, now again... Is Salesforce committed to Heroku?

Heroku has brought our site down 5 times in the last 6 months. It's infuriating, but I only have myself to blame for not migrating.
Post reply on HN