Issues with upstream DNS provider • Hacker News Board

Re: Issues with upstream DNS provider

#121

Post by iuliu » Wed, Aug 24, 2022, 1:06 AM UTC

jamesr101 wrote: post #118

iuliu wrote: post #112

Earlier quoted context omitted.

Do you use Cloudflare?

No we just run our API on heroku and use no custom domain names. For some of us requests are working as normal, but for others every request is failing.

What error are you getting? Because for us it seemed that the Cloudflare HerokuDNS link was down. But even then I was able to access my app from the dashboard (like https://my-app.herokuapp.com/)

Re: Issues with upstream DNS provider

#122

Post by iuliu » Wed, Aug 24, 2022, 1:12 AM UTC

It seems that their service is back up

Re: Issues with upstream DNS provider

#123

Post by seoneehills » Wed, Aug 24, 2022, 1:12 AM UTC

exitnode_ttl0 wrote: post #100

I am now seeing one of my services coming back online. For this service I have not replaced the CNAME. Anyone else seeing some service restoration as well?

Same boat for me. How long do you think you'll wait to go back to CNAME's?

Re: Issues with upstream DNS provider

#124

Post by nightpool » Wed, Aug 24, 2022, 1:15 AM UTC

Weirdly, dig +trace works fine, but public resolvers like Google and Cloudflare refuse to return the DNS records. This has to be a DNSSEC issue, right? paging tptacek :p

Re: Issues with upstream DNS provider

#125

Post by ab-dm » Wed, Aug 24, 2022, 1:15 AM UTC

I've swapped the A records back to the CNAME and all is looking good. The Heroku Dashboard still isn't loading app details though.

Re: Issues with upstream DNS provider

#126

Post by exitnode_ttl0 » Wed, Aug 24, 2022, 1:16 AM UTC

seoneehills wrote: post #123

exitnode_ttl0 wrote: post #100

I am now seeing one of my services coming back online. For this service I have not replaced the CNAME. Anyone else seeing some service restoration as well?

Same boat for me. How long do you think you'll wait to go back to CNAME's?

I went back to the CNAME now and everything is up and running. Fingers crossed that Heroku reports to have the issues resolved.

Re: Issues with upstream DNS provider

#127

Post by fusionflo » Wed, Aug 24, 2022, 1:16 AM UTC

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! You saved our ass.

Re: Issues with upstream DNS provider

#128

Post by hluska » Wed, Aug 24, 2022, 1:21 AM UTC

exitnode_ttl0 wrote: post #100

I am now seeing one of my services coming back online. For this service I have not replaced the CNAME. Anyone else seeing some service restoration as well?

Our service started coming back up around twenty minutes ago too.

Re: Issues with upstream DNS provider

#129

Post by rafaparadela » Wed, Aug 24, 2022, 1:24 AM UTC

It worked for us too. Thanks.

Note: If you used to have a CNAME record for yourdomain.com to www.yourdomain.com, then you have to add two A records per each IP (one whose name is yourdomain.com pointing to the IP, and another whose name is www pointing to the same IP)

Re: Issues with upstream DNS provider

#130

Post by rafaparadela » Wed, Aug 24, 2022, 1:28 AM UTC

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…

It worked for us too. Thanks.

Note: If you used to have a CNAME record for yourdomain.com to www.yourdomain.com, then you have to add two A records per each IP (one whose name is yourdomain.com pointing to the IP, and another whose name is www pointing to the same IP)