-
Notifications
You must be signed in to change notification settings - Fork 157
Massdns script issue #9
Comments
I have a feeling its because its pulling down the latest branch release of massdns 0.3 |
Thanks @z3roskills for reporting the issue! @jafoca issued a pull request (#10) that should fix the issue (after fresh install), can you please confirm? |
I just checked on a Ubuntu fresh install and i am getting the following error
|
@z3roskills, sorry for the delay - are you still receiving the same error? Looks like you had a permission denied error and a python error as well. What version of python are you using? |
Thanks @z3roskills! Please let me know if there are any additional issues. |
Hello @cak The problem was not resolved. must remove the "-a" option and add S option.
|
Looking at the massdns documentation and I you are right! Reopening, thanks @oldesec. |
Hello. @cak Good patch. There is one more problem. "massdns" is using an older version. It is necessary to change to the latest version. Ex)
|
@oldesec Do you still have problem with this? |
still massdns problem root@kalitest:~/domained# python3 domained.py -d site.com -b --bruteall
Running massdns Running Command: python /root/domained/bin/subbrute/subbrute.py /root/domained/bin/sublst/all.txt site.com | /root/domained/bin/massdns/bin/massdns -r resolvers.txt -t A -o S -w output/site.com-massdns.txt Masscan Complete |
Is your script upto date? |
yeap, last release |
I am experiencing the same issue |
I think I found the issue. I'll test again in the next day or so. |
Anyone actually successful in fixing this? |
When running domained.py with the following parameters:
python domained.py -d example.com -b --bruteall
I get the following output:
I was able to look into the previous resolved issue #8 and noticed from the MASSDNS documentation that the -a flag appears to no longer be an option. Also the -o flag will require S,F or B flag for its output.
Example of changes i made to the script locally.
Once i get these things fixed up the script kicks off but never actually starts running just sits idle as can be seen here.
Ive tried this on 2 separate Kali instances with the same results.
Running the following command from within the massdns directory i start getting instant results.
The text was updated successfully, but these errors were encountered: