Open prasgop opened 3 months ago
I cannot reproduce this. This does not look like output from massdns. It looks like the error message from a Go binary, cf. https://go.dev/src/flag/flag.go.
// errParse is returned by Set if a flag's value fails to parse, such as with an invalid integer for Int.
// It then gets wrapped through failf to provide more information.
var errParse = errors.New("parse error")
MassDNS's source code does not contain this error string. Given that you have also created an issue in the shuffledns repo (https://github.com/projectdiscovery/shuffledns/issues/293), is it possible that you have supplied the -t
parameter to shuffledns?
No, I have not mentioned -t or an output file for shuffledns command (shuffledns command was the one I mentioned under shuffledns issue #293).
While trying to figure out, I wanted to uninstall massdns and reinstall to check again. Initially, I did - git clone ... cd massdns make sudo make install
and, I could see /usr/local/bin/massdns but when running, I was seeing that 'could not run massdns: ..' error mentioned under 'shuffledns' issue (#293).
Later I uninstalled and reinstalled as - git clone ... cd massdns make sudo cp ~/massdns/bin/massdns /usr/local/bin/
Not sure how but I was not seeing the 'could not run massdns: ..' error now. I think, it has started running. However, it's been more than 3 hours and I am yet to see an update or the 'finished resolving' message. I could see it running by using 'top' command. The delay may be because of the huge wordlist I used (assetnote best-dns-wordlist). I should have used a small file first to make sure it's working. I want to leave kali open for a bit more and see if resolving finishes giving any results. Then, I will try with a small file and see if it's working or not.
massdns and shuffledns are working now after doing the reinstall I mentioned earlier.
Just that I am not able to use net while shuffledns/massdns is running dns resolution. and, it is taking like forever if I used a large wordlist and I am giving up after few hours. I waited for an hour when using "subdomains-top1million-110000.txt" from seclists and gave up then, but when I changed the wordlist to 'subdomains-top1million-5000.txt', I could finally see shuffledns completing the task and showing result in about 5 minutes. May be it's something to do with my system config and not an issue with the tools?
Not able to DNS resolve using massdns when the output from dnsgen is used.
![ss3](https://github.com/blechschmidt/massdns/assets/116869728/efbe3475-7ef3-4679-8f3c-fae8d96d35b7)