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

51–60 of 159 posts

Re: Issues with upstream DNS provider

#51

Post by bobsingor »

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…

Wow this worked! Your amazing! Thank you so much

Re: Issues with upstream DNS provider

#52

Post by jeffbee »

zinekeller wrote: post #28
jeffbee wrote: post #15

Other Cloudflare-backed services like Observable are offline right now. Is it a Cloudflare outage?

More likely that Cloudflare is unable to access downed servers.

Maybe. I'm just trying to figure out what's common between Steam, Observable, and Heroku, and Cloudflare itself which are all down according to downdetector.

Re: Issues with upstream DNS provider

#53

Post by rajamaka »

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…

No historical DNS records on that site for us unfortunately, any other possible sites to check?

Re: Issues with upstream DNS provider

#54

Post by fourstar »

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 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).

Re: Issues with upstream DNS provider

#55

Post by mbesto »

reaperducer wrote: post #32
hamhamed wrote: post #6

Immediately came to HN, best status server

I wonder if some clever person could build a routine to grep HN headlines and build a multi-service outage dashboard from what suddenly gets popular.

I'm building a service to create a forum, a la HN style, for service incidents.

If you're interested in getting early access - get in touch here: hello@awareops.com

Re: Issues with upstream DNS provider

#56

Post by cyral »

rajamaka wrote: post #53
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…

No historical DNS records on that site for us unfortunately, any other possible sites to check?

Try this command: nslookup DOMAIN 212.230.255.1

That is a random public DNS server I found on a DNS checker site that works (as it seems to be down from all the common ones like 8.8.8.8, 1.1.1.1, etc). DOMAIN can be your actual domain or the long heroku alias.

Re: Issues with upstream DNS provider

#57

Post by tdehnke »

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…

Woot! Thank you - that seems to work, just used the first IP that came up on ST (there were 4 listed).

Re: Issues with upstream DNS provider

#58

Post by exitnode_ttl0 »

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…

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?

Re: Issues with upstream DNS provider

#59

Post by kennysmoothx »

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 worked for us, thank you.

And for those using Cloudflare, this method works.

Re: Issues with upstream DNS provider

#60

Post by Maarius »

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…

Thanks so much, worked for us as well. I created A records for all three of the listed IP addresses but it started working for the first one already.
Post reply on HN