News for hackers. Stuff that matters.
Re:Issues with upstream DNS provider by bfirsh on Tuesday August 23, 2022 @08:01PM (#32573272)
You need to put in the herokudns.com address that the CNAME is pointing at – e.g. stark-wisteria-rnbgkawldfk6gq7m8308ytts.herokudns.com in our case.
Re:Issues with upstream DNS provider by iuliu on Tuesday August 23, 2022 @08:32PM (#32573531)
For me the securitytrails.com website just crashes. I put my DNS target: "stark-horse-mrp4jeowu9yvwpnnma32x6hd.herokudns.com", clicked "Run Check" and it seems to redirect to a failed (no CSS) webpage. Anyone else experiencing this?

EDIT: I MANAGED to make it work with this:

https://www.nslookup.io/

Make sure to go through all the tabs at the top (Cloudflare DNS, Google DNS) - for me they were all "no A records found". Only "Authoritative" gave me 3 A records which I successfully managed to use.

Re:Issues with upstream DNS provider by eappleby on Tuesday August 23, 2022 @08:48PM (#32573640)
That seems to happen when you put in a DNS target that doesn't have any records in SecurityTrails. In that case, it is best to use nslookup
Re:Issues with upstream DNS provider by jonathanreinink on Tuesday August 23, 2022 @08:40PM (#32573587)
Yeah securitytrails.com was working for me, but went down about 10 mins ago.
Re:Issues with upstream DNS provider by jplehmann on Tuesday August 23, 2022 @08:39PM (#32573579)
Thanks so much, it worked for us.