This repository has been archived by the owner on Apr 11, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 157
massdns error #19
Comments
@RnmX Thanks for reporting the issue (and the fix!) with the massdns command! If you would like to do a pull request I will get it tested and merged ASAP or if not I can update and push out. |
@RnmX Thank you for your patience. I am still testing this to ensure that removing the |
Hello there! Sorry for not replying but I was off for holidays. How is your testing going? |
@RnmX Sorry for the delay, I validated and pushed your fix for MassDNS. Please let me know if any other issues. Thanks again! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hello guys,
I was experimenting with this tools recently I and found it's current implementation does not work well with massdns. I noticed the sublister which is used by domained (/bin/sublister/sublister.py) behaves differently from sublister.py which is presented in /bin/massdns/sublister.py. If I run "python domained.py -b domain.com -b --bruteall" I never actually get to see massdns's "status screen" and it looks like it got stuck.
I was able to make it work by changing these lines:
massdnsCMD = 'python {} -s {} {} | {} -r resolvers.txt -t A -a -o -w {}-massdns.txt -'.format(
os.path.join(script_path, 'bin/subbrute/subbrute.py'), word_file, domain,
to look like this:
massdnsCMD = 'python {} {} {} | {} -r resolvers.txt -t A -a -o -w {}-massdns.txt -'.format(
os.path.join(script_path, 'bin/massdns/subbrute.py'), word_file, domain,
Then it works perfectly fine.
Thanks!
The text was updated successfully, but these errors were encountered: