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

81–90 of 159 posts

Re: Issues with upstream DNS provider

#81

Post by cyral »

Trasmatta wrote: post #73
ab-dm wrote: post #66

Earlier quoted context omitted.

I thought about this, and it can't really get any worse than 'total outage', so I thought it was worth taking a shot. It can't go any more down. It worked for me, so once Heroku has sorted their s*t out and their DNS system is back up it's just a matter of deleting the A records and replacing it with the CName. Worst case scenario is the underlying Amazon IP Addresses change and it goes back down.

Wouldn't the worst case be the underlying IP address changes, and your site now points to some other service? Since Heroku doesn't offer static IPs, I don't think.

Heroku seems to use the Host header on the HTTP request to determine what customer the request is sent to, so I don't think it can end up somewhere it shouldn't be unless the IP leaves control of Heroku entirely and is picked up by another AWS customer.

Re: Issues with upstream DNS provider

#82

Post by kwentakill »

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…

Working well !

Re: Issues with upstream DNS provider

#83

Post by bjoveski »

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…

Thank you a lot!!

Re: Issues with upstream DNS provider

#84

Post by ab-dm »

mtlynch wrote: post #43
bobsingor wrote: post #30

Earlier quoted context omitted.

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.

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

Re: Issues with upstream DNS provider

#85

Post by iuliu »

bfirsh wrote: post #46
theunixbeard wrote: post #45

Earlier quoted context omitted.

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.

For me the securitytrails.com website just crashes. I put my DNS target: "stark-horse-mrp4jeowu9yvwpnnma32x6hd.herokudns.com", clicked "Run Check" and it seems to redirect to a failed (no CSS) webpage. Anyone else experiencing this?

EDIT: I MANAGED to make it work with this:

https://www.nslookup.io/

Make sure to go through all the tabs at the top (Cloudflare DNS, Google DNS) - for me they were all "no A records found". Only "Authoritative" gave me 3 A records which I successfully managed to use.

Re: Issues with upstream DNS provider

#86

Post by dogweather »

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.

Re: Issues with upstream DNS provider

#87

Post by jplehmann »

bfirsh wrote: post #46
theunixbeard wrote: post #45

Earlier quoted context omitted.

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.

Thanks so much, it worked for us.

Re: Issues with upstream DNS provider

#88

Post by jonathanreinink »

iuliu wrote: post #85
bfirsh wrote: post #46

Earlier quoted context omitted.

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.

For me the securitytrails.com website just crashes. I put my DNS target: "stark-horse-mrp4jeowu9yvwpnnma32x6hd.herokudns.com", clicked "Run Check" and it seems to redirect to a failed (no CSS) webpage. Anyone else experiencing this? EDIT: I MANAGED to make it work with this: https://www.nslookup.io/ Make sure to go through all the tabs at the top (Cloudflare DNS, Google DNS) - for me they were all "no A records found…

Yeah securitytrails.com was working for me, but went down about 10 mins ago.

Re: Issues with upstream DNS provider

#89

Post by rajamaka »

cyral wrote: post #56
rajamaka wrote: post #53

Earlier quoted context omitted.

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.

You bloody legend, thanks!

Re: Issues with upstream DNS provider

#90

Post by estafaa »

rsweeney21 wrote: post #69
theunixbeard wrote: post #45

Earlier quoted context omitted.

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?

We use cloudflare. If you look up the IP address for your public domain name, you will get the cloudflare IP, yes. If you lookup the IP address of the CNAME target, you will get the heroku IP.

on Cloudflare do you create A records (with found IPs) with name "www" or "mydomain.com"? also do you make that A record proxied or no? Thank you!
Post reply on HN