Issues with upstream DNS provider • Hacker News Board

Re: Issues with upstream DNS provider

#21

Post by bobby_growth » Tue, Aug 23, 2022, 11:43 PM UTC

Heroku. DansGame.

Re: Issues with upstream DNS provider

#22

Post by bfirsh » Tue, Aug 23, 2022, 11:45 PM UTC

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-wisteria-rnbgkawldfk6gq7m8308ytts.herokudns.com. IN A

I wonder if there is any way to get out an IP address of the Heroku router we were assigned to that we can use in place of the CNAME.

Might be in the logs somewhere, or in Cloudflare somewhere?

Re: Issues with upstream DNS provider

#23

Post by daveguy » Tue, Aug 23, 2022, 11:46 PM UTC

hamhamed wrote: post #6

Immediately came to HN, best status server

Same. If I am having a problem with a site but nothing else, next step is HN.

Re: Issues with upstream DNS provider

#24

Post by antod » Tue, Aug 23, 2022, 11:47 PM UTC

md224 wrote: post #14

TIL Substack runs on Heroku.

They might just have the same upstream DNS provider?

Re: Issues with upstream DNS provider

#25

Post by mcint » Tue, Aug 23, 2022, 11:48 PM UTC

Seeing issues with hackerweb.app and substack.com too.

They don't share upstream DNS (and I'm not sure heroku's homepage has the same DNS provider as customer domains). NS matches SOA for each of these domains.

    SOA heroku.com.    1h00m00s   "dns1.p04.nsone.net." "hostmaster.nsone.net."
    SOA hackerweb.app. 1h00m00s   "olga.ns.cloudflare.com." "dns.cloudflare.com."
    SOA substack.com.  1h00m00s   "ali.ns.cloudflare.com." "dns.cloudflare.com."

Re: Issues with upstream DNS provider

#26

Post by ezekg » Tue, Aug 23, 2022, 11:48 PM UTC

All services are completely down for my business.

Looks like they nuked their DNS.

Re: Issues with upstream DNS provider

#27

Post by zinekeller » Tue, Aug 23, 2022, 11:48 PM UTC

md224 wrote: post #14

TIL Substack runs on Heroku.

Seems to be (https://substack.statuspage.io/incidents/7ct4mgnd5dhn)

Re: Issues with upstream DNS provider

#28

Post by zinekeller » Tue, Aug 23, 2022, 11:49 PM UTC

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.

Re: Issues with upstream DNS provider

#29

Post by mr90210 » Tue, Aug 23, 2022, 11:49 PM UTC

jeffbee wrote: post #15

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

https://www.cloudflarestatus.com/

Re: Issues with upstream DNS provider

#30

Post by bobsingor » Tue, Aug 23, 2022, 11:49 PM UTC

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?