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

31–40 of 159 posts

Re: Issues with upstream DNS provider

#31

Post by tortilla »

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?

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

Re: Issues with upstream DNS provider

#35

Post by rsweeney21 »

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. We plan to revert back to CNAME records once Heroku gets their DNS issues sorted.

Re: Issues with upstream DNS provider

#36

Post by rajamaka »

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?

Moving to ECS on AWS, only reason is that I'm a DevOps engineer with familiarity in that space. Honestly wouldn't know where to send developers without the time to figure the nuts and bolts of convenience that Heroku provides.

Re: Issues with upstream DNS provider

#37

Post by john37386 »

bfirsh wrote: post #22

Looks like just DNS for the CNAME is broken. $ dig @1.1.1.1 stark-wisteria-rnbgkawldfk6gq7m8308ytts.herokudns.com A ... ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 1232 ; OPT=15: 00 09 6e 6f 20 53 45 50 20 6d 61 74 63 68 69 6e 67 20 74 68 65 20 44 53 20 66 6f 75 6e 64 20 66 6f 72 20 68 65 72 6f 6b 75 64 6e 73 2e 63 6f 6d 2e ("..no SEP matching the DS found for herokudns.com.") ;; QUESTION SECTION: ;stark-w…

no SEP matching is a dnssec error. The DS key in the .com. zone file are there but no longer available in herokudns.com.

Hopefully someone has a backup of those keys. If not, I think they have to contact .com. to replace the keys. It can take several hours to come back.

Re: Issues with upstream DNS provider

#38

Post by zzh8829 »

Looks like Heroku uses NS1 as the upstream DNS provider. you can find the information like this

  dig NS @1.1.1.1 test.herokuapp.com -> fail

  dig @1.1.1.1 test.herokuapp.com -> fail

  dig NS @dns1.p03.nsone.net test.herokuapp.com -> works

  dig @dns1.p03.nsone.net test.herokuapp.com -> works
So my conclusion is that NS1 is having issue responding DNS queries from other DNS servers. Interestingly, there is no public information on heroku being dependent on NS1 or any current outages from NS1 status page.
Post reply on HN