101–110 of 159 posts
Earlier quoted context omitted.
No historical DNS records on that site for us unfortunately, any other possible sites to check?
This one worked for me: https://dnshistory.org/
Unfortunately the Heroku issue lost us a few thousand $ alongside a few customers.
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!
Earlier quoted context omitted.
Hi all, deleting a root CNAME record and adding a new A record on Cloudflare was too risky for us, with its potential to impact external DNS responses, so we took the following steps instead: 1. Create a new temporary subdomain in the Cloudflare DNS panel, e.g. "temp-heroku-resolve.your-domain.com", with IPs from the responses you get by querying Heroku's upstream provider directly (`dig @1.1.1.1 +trace your-app.hero…
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)
Earlier quoted context omitted.
Hi all, deleting a root CNAME record and adding a new A record on Cloudflare was too risky for us, with its potential to impact external DNS responses, so we took the following steps instead: 1. Create a new temporary subdomain in the Cloudflare DNS panel, e.g. "temp-heroku-resolve.your-domain.com", with IPs from the responses you get by querying Heroku's upstream provider directly (`dig @1.1.1.1 +trace your-app.hero…
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)
In our case, we have substantial logic running on the edge in Cloudflare Workers, as well as lots of other Cloudflare configuration options, and I don't even want to know what it could potentially do to our zone to remove the root DNS record that everything's tied to.
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…
Anyone know how to make this work for a subdomain?
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 just happened to try out Render last week - perfect timing.
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.
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…