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

131–140 of 159 posts

Re: Issues with upstream DNS provider

#131

Post by xofer »

exitnode_ttl0 wrote: post #96
nightpool wrote: post #95

Earlier quoted context omitted.

Hi all, deleting a root CNAME record and adding a new A record on Cloudflare was too risky for us, with its potential to impact external DNS responses, so we took the following steps instead: 1. Create a new temporary subdomain in the Cloudflare DNS panel, e.g. "temp-heroku-resolve.your-domain.com", with IPs from the responses you get by querying Heroku's upstream provider directly (`dig @1.1.1.1 +trace your-app.hero…

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)

Deleting a record causes requests for that record to be negatively cached. The negative cache TTL[1] is often set to 1 day. So, deleting and immediately recreating a record can take your site offline for days. (Source: I made this mistake when changing a Route53 record for a subdomain that was getting about 70Krps. Luckily it was our source code making the requests, so we could change it, but that took an hours or so to roll out.)

[1]: https://www.rfc-editor.org/rfc/rfc2308

Re: Issues with upstream DNS provider

#134

Post by dogweather »

tortilla wrote: post #31
bobsingor wrote: post #30

Earlier quoted context omitted.

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

I'm looking at fly.io and render.com.

I just completed the move of my web app to render, and for now connecting back to Heroku for the postgres instance. I'll move that over eventually.

Re: Issues with upstream DNS provider

#135

Post by tuxninja »

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…

Yes, this worked for me...I was trying to do this right away, but I was missing a way to find historical DNS, thank you!!

Re: Issues with upstream DNS provider

#136

Post by benschwarz »

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?

My company moved a 600GB postgres db to crunchydata (https://www.crunchydata.com), the process was super smooth. In fact, it went so well that I agreed to a quick case study: https://www.crunchydata.com/case-studies/calibre.

We're currently using Heroku for app hosting, while evaluating fly.io, render.com and railway.app. All three have had exceptional reviews from other customers and differ slightly on their service offerings and setups. All seem like viable alternatives so far!

Re: Issues with upstream DNS provider

#138

Post by ezekg »

ab-dm wrote: post #78
jarym wrote: post #62

Earlier quoted context omitted.

And the new product might have to be put on hold until Heroku is back… catch-22 - you’ll never migrate away

Well, the new product is hosted on AWS, so it's much more stable, and we've made our first lot of pre-sales so we're on a tight deadline. Not sure why you're being so negative for no reason.

I think they were being funny... :)

Re: Issues with upstream DNS provider

#139

Post by mtlynch »

ab-dm wrote: post #84
mtlynch wrote: post #43

Earlier quoted context omitted.

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

Did you use the https://fly.io/launch/heroku migration page? It almost looks too good to be true.

No, I wasn't using much Heroku-specific. All of my apps run in Docker containers, so it's mostly just migrating my CI to deploy to Fly instead of Heroku.

I did get a lot of perf increases moving from GCP to Fly, but I think I have to credit most of the improvements to SQLite being faster than Firestore:

https://mtlynch.io/retrospectives/2021/12/#migrating-my-side...

Re: Issues with upstream DNS provider

#140

Post by ab-dm »

ezekg wrote: post #138
ab-dm wrote: post #78

Earlier quoted context omitted.

Well, the new product is hosted on AWS, so it's much more stable, and we've made our first lot of pre-sales so we're on a tight deadline. Not sure why you're being so negative for no reason.

I think they were being funny... :)

Then they should have added a smiley face :p
Post reply on HN