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

141–150 of 159 posts

Re: Issues with upstream DNS provider

#141

Post by anurag »

fourstar wrote: post #54
tortilla wrote: post #31

Earlier quoted context omitted.

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

I moved from Heroku to Render. Can't recommend them enough. Smaller operation, of course so keep that in mind if you need support, but for a hobbyist like myself, I'm running 2 postgres dbs, 1 redis instance, and 4 web services (2 websites).

(Render founder) thanks for the rec and feel free to get in touch with me anytime (email in profile). For those who need them, we offer enterprise support plans with response and uptime SLAs.

Re: Issues with upstream DNS provider

#142

Post by mtlynch »

nicoburns wrote: post #97
mtlynch wrote: post #43

Earlier quoted context omitted.

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

How have you found uptime on fly.io (and are you using multiple instances for a high-availability setup?). We've been running on Heroku without HA, and it's been good enough, and wondering if we might expect to be able to get away with that on fly.io too...

Uptime has mostly been good, although I didn't set up alerting for any of my Fly projects until recently. All my apps are running on a single node per app, so I haven't tried

The one notable outage was this bug where Fly was evicting smaller instances at overloaded DCs rather than preventing new apps from acquiring resources:

https://community.fly.io/t/app-stuck-in-pending-state-after-...

The workaround was to upgrade to a larger instance, but I probably evicted someone else.

Re: Issues with upstream DNS provider

#143

Post by csjh »

dogweather wrote: post #86
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…

Nice. We got our test site online by migrating just the dyno to render.com. (And connecting back to Heroku for the database.) We might just switch our DNS there and call it a permanent move.

probably worth staying at render considering how many issues heroku's had recently

Re: Issues with upstream DNS provider

#144

Post by muvb00 »

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…

Worked... thanks a bunch. Does anyone know if it's safe to go back to cname now or should I leave till the A record till the morning? Would prefer to get some sleep.

Re: Issues with upstream DNS provider

#145

Post by bombcar »

nightpool wrote: post #104
exitnode_ttl0 wrote: post #96

Earlier quoted context omitted.

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)

The advantage is that you can do the CNAME swap atomically in the Cloudflare interface, instead of deleting a CNAME record and adding a new A record, which would lead to a few seconds when your DNS is entirely removed. Those few seconds may not sound like a lot, but they could be cached by Cloudflare or other external DNS resolvers, trigger "clean-up" functions within Cloudflare to remove resources associated with th…

Sounds like cloudflare could add an atomic cname -> a record feature.

Re: Issues with upstream DNS provider

#146

Post by fhte »

bombcar wrote: post #145
nightpool wrote: post #104

Earlier quoted context omitted.

The advantage is that you can do the CNAME swap atomically in the Cloudflare interface, instead of deleting a CNAME record and adding a new A record, which would lead to a few seconds when your DNS is entirely removed. Those few seconds may not sound like a lot, but they could be cached by Cloudflare or other external DNS resolvers, trigger "clean-up" functions within Cloudflare to remove resources associated with th…

Sounds like cloudflare could add an atomic cname -> a record feature.

Cloudflare should support RFC 2136 which includes atomic updates and is the standard for DNS updates.

Re: Issues with upstream DNS provider

#147

Post by alexthehurst »

benschwarz wrote: post #136
bobsingor wrote: post #30

Earlier quoted context omitted.

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 serv…

For what it's worth: Crunchydata appears to have been using Heroku DNS in some way. We have a Heroku app with Crunchy databases, and our Crunchy dbs became inaccessible shortly before the app did.

Re: Issues with upstream DNS provider

#149

Post by geoffharcourt »

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?

We moved our app to Porter after the credentials incident this spring and have been very pleased.

Re: Issues with upstream DNS provider

#150

Post by rsavage »

benschwarz wrote: post #136
bobsingor wrote: post #30

Earlier quoted context omitted.

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 serv…

I’d be really interested to know how your research goes. We are running a large production scale app on heroku. And that we have no DevOps or Infra staff is awesome. But heroku has been a huge let down lately.

Most of the reviews we have seen of the competitors are all hobby level. And last time we check some of this competitors we found their security posture was not the level we would require.

So we had to simple rule them out and either stay with Heroku or move to a big 3.

If you’re keen to share - let me know and I’ll send you my details.

Post reply on HN