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

111–120 of 159 posts

Re: Issues with upstream DNS provider

#111

Post by alexpoof »

estafaa wrote: post #90
rsweeney21 wrote: post #69

Earlier quoted context omitted.

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!

For my domain (https://www.poof.io), it's www.

If you just use something like https://poof.io, then it would be @. Depends on your site.

There should be a few historical IP addresses, but you would create an A record for each of them.

Re: Issues with upstream DNS provider

#112

Post by iuliu »

jamesr101 wrote: post #109
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…

Can someone clarify what to do if your app doesn't use a custom domain, and running `heroku domains -a` just returns `my_app.herokuapp.com`, and then entering that into https://securitytrails.com/dns-trails returns no results?

Do you use Cloudflare?

Re: Issues with upstream DNS provider

#113

Post by exitnode_ttl0 »

nightpool wrote: post #104
exitnode_ttl0 wrote: post #96

Earlier quoted context omitted.

This is essentially doing the same thing right? What is the advantage of this method? Less DNS changes? (not trying to be snarky, trying to understand)

The advantage is that you can do the CNAME swap atomically in the Cloudflare interface, instead of deleting a CNAME record and adding a new A record, which would lead to a few seconds when your DNS is entirely removed. Those few seconds may not sound like a lot, but they could be cached by Cloudflare or other external DNS resolvers, trigger "clean-up" functions within Cloudflare to remove resources associated with th…

Good points, thanks!

Re: Issues with upstream DNS provider

#116

Post by johnnymetz »

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. We're using Heroku + Cloudflare.

Re: Issues with upstream DNS provider

#117

Post by 0xChain »

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 saved our bacon and got me a pat on the back from our VP. Thanks!

Re: Issues with upstream DNS provider

#118

Post by jamesr101 »

iuliu wrote: post #112
jamesr101 wrote: post #109

Earlier quoted context omitted.

Can someone clarify what to do if your app doesn't use a custom domain, and running `heroku domains -a` just returns `my_app.herokuapp.com`, and then entering that into https://securitytrails.com/dns-trails returns no results?

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.

Re: Issues with upstream DNS provider

#119

Post by Justsignedup »

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…

You and your team are brilliant. Thank you for this post! Much love.
Post reply on HN