Unable to find authoritative resolvers for:google.com about subbrute HOT 9 CLOSED

dig NS +tcp google.com @8.8.8.8
;; Connection to 8.8.8.8#53(8.8.8.8) for google.com failed: connection refused.

from subbrute.

I think this issues is ISP dependent because when i tried using a different ISP it all work like a charm.

from subbrute.

Interesting bug report. I think this is a valid issue, try changing the resolvers.txt to your ISP's resolvers, does this fix the problem?

With your limited connection, can you resolve on 8.8.8.8?
dig google.com @8.8.8.8

from subbrute.

same error " Unable to find authoritative resolvers for:google.com "

i also changed resolvers.txt to my ISP Resolver .

dig google.com @8.8.8.8

; <<>> DiG 9.9.5-9+deb8u2-Debian <<>> google.com @8.8.8.8
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 17239
;; flags: qr rd ra; QUERY: 1, ANSWER: 11, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 172 IN A 173.194.116.201
google.com. 172 IN A 173.194.116.206
google.com. 172 IN A 173.194.116.192
google.com. 172 IN A 173.194.116.199
google.com. 172 IN A 173.194.116.200
google.com. 172 IN A 173.194.116.195
google.com. 172 IN A 173.194.116.194
google.com. 172 IN A 173.194.116.193
google.com. 172 IN A 173.194.116.198
google.com. 172 IN A 173.194.116.196
google.com. 172 IN A 173.194.116.197

;; Query time: 204 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Sun Apr 03 04:51:48 EDT 2016
;; MSG SIZE rcvd: 215

from subbrute.

I'm hitting the same problem after switching to Google's 8.8.8.8/8.8.4.4 nameservers: i currently avoid this error by using OpenDNS instead echo -e "208.67.222.222\n208.67.220.220" > opendns.txt.

from subbrute.

I have the same problem, any domain I try, like:
python subbrute.py google.com
"Unable to find authoritative resolvers for: google.com"
It can't have anything to do with any ISP I would think.

from subbrute.

Does dig work with TCP, or only UDP?

dig NS +tcp google.com @8.8.8.8

The command above and subbrute work great on mysystem, which makes this
issue exceeding difficult to patch. I'd be happy to merge a pull request
if you can figure out why it won't work on your systems

subbrute> python subbrute.py google.com -p
google.com,A,216.58.194.206
google.com,AAAA,2607:f8b0:4005:805::200e
google.com,MX,50 alt4.aspmx.l.google.com.
google.com,MX,10 aspmx.l.google.com.
google.com,NS,ns3.google.com.
google.com,NS,ns2.google.com.
google.com,NS,ns4.google.com.
...

On Mon, Oct 3, 2016 at 12:22 AM, PePa [email protected] wrote:

I have the same problem, any domain I try, like:
python subbrute.py google.com
"Unable to find authoritative resolvers for: google.com"
It can't have anything to do with any ISP I would think.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#34 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf2Nx9BXm1IzxwTwyikEV4kWPz2UNBsks5qwK1NgaJpZM4Hq_Yi
.

from subbrute.

@pepa65 Try hooking to a different network, preferably with a different ISP and share the result. I honest failed to understand this but all i can say is that it worked with no problem after switching my ISP.

from subbrute.

If your ISP is blocking access to the resolvers with -r, then all I can do
for you is VPN access XD

Good luck guys.

On Mon, Oct 3, 2016 at 10:48 AM, ronnieflip [email protected]
wrote:

@pepa65 https://github.com/pepa65 Try hooking to a different network,
preferably with a different ISP and share the result. I honest failed to
understand this but all i can say is that it worked with no problem after
switching my ISP.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
#34 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAf2NyDXKQ9mQpI-l8Bs1BaokyYS5Fq2ks5qwT_9gaJpZM4Hq_Yi
.

from subbrute.