Bug: ShuffleDNS hangs when trying to remove wildcards despite a domain not being given.

[projectdiscovery]

Bug: ShuffleDNS hangs when trying to remove wildcards despite a domain not being given.

[JeffreyShran]

It might help so I ran my command again with the -d parameter and got the same behaviour. I only waited a couple of minutes this time though.

cat shorty.txt | shuffledns -w "commonspeak2.txt" -r "dnsvalidator/resolvers.txt" -o shuffledns.txt -d atlassian.net

If I watch it in htop the process barely uses any CPU/RAM as if it's stopped doing anything useful.

[ehsandeep]

Hi @JeffreyShran,

Yes, to use the wildcard filter feature, you always need to use d flag.

I do see the issue with the command you are running here.

cat shorty.txt | shuffledns -w "commonspeak2.txt" -r "dnsvalidator/resolvers.txt" -o shuffledns.txt -d atlassian.net

where shorty.txt contains a list of subdomains, and commonspeak2.txt list of words to bruteforce, with shuffledns you can perform both a) bruteforce b) resolving action, but not both at same time which you doing in this case, so the right command should be:-

Resolve + Wildcard Filter

cat shorty.txt | shuffledns -r "dnsvalidator/resolvers.txt" -o shuffledns.txt -d atlassian.net

Bruteforce + Wildcard Filter

shuffledns -r "dnsvalidator/resolvers.txt" -w "commonspeak2.txt" -o shuffledns.txt -d atlassian.net

[JeffreyShran]

Thanks. That makes complete sense. I thought that I could just throw it all in and it would somehow work.