search

pry0cc / axiom

The dynamic infrastructure framework for everybody! Distribute the workload of many different scanning tools with ease, including nmap, ffuf, masscan, nuclei, meg and many more!
MIT License
4k stars 622 forks source link

DNSX module not working properly #482

Closed Sicks3c closed 2 years ago

Sicks3c commented 2 years ago

Summary

Hello Team I noticed that dnsx is not working properly I was trying to give it a list of unresolved subs and it doesn't perform any test

POC

Screen Shot 2021-10-28 at 13 56 00

Cheers

0xtavian commented 2 years ago

@Sicks3c Odd. That exact same command works for me. Any chance you are using an older version of dnsx? Maybe try running axiom-update and axiom-build again? Other tools are working for you?

Sicks3c commented 2 years ago

Hello @0xtavian I have successfully updated the axiom and rebuild again and I'm facing the same issue again

Regards

pdelteil commented 2 years ago

Hello @0xtavian I have successfully updated the axiom and rebuild again and I'm facing the same issue again

Regards

hi there,

Show the output of these commands:

wc -l unique cat dns.txt #output?

19k targets is not a lot for a tool like dnsx since resolving hosts is much faster than performing http requests. (each instance is doing 2,180 targets)

0xtavian commented 2 years ago

@Sicks3c if you can run axiom-scan with --debug, remove any sensitive information and post it here, I should be able to figure out whats wrong. Feel free to join us on discord as well.

It is happening with all tools or just DNSx?

Sicks3c commented 2 years ago

@0xtavian

Nah It happens for hakrawler but it's a different scenario it shows that the tools is available in module but it's not

Screen Shot 2021-10-29 at 14 39 23

Send discord invitation

0xtavian commented 2 years ago

@Sicks3c can you cd in ~/.axiom and run git pull and lmk if there are any errors? What OS are you using for your axiom-controller? I havent been able to reproduce this at all. You seem to be missing a lot of tools. I suspect you're using an old provisioner https://github.com/pry0cc/axiom/tree/master/images/provisioners and have made some local changes to .axiom causing axiom-update ( just a git pull redirecting output to /dev/null) to silently fail.

Sicks3c commented 2 years ago

Hello @0xtavian

I have done the git pull on ~/.axiom nothing new was pulled and I run with debug and here's the output

debug.txt

0xtavian commented 2 years ago

@Sicks3c I would follow these steps to delete axiom and reinstall. I would also delete any previously saved images with axiom-images and then run axiom-configure, which will make a new image etc.

A better approach is to provision a new cloud hosted ubuntu 20.04 machine from the cloud providers web gui, ssh into the droplet, run sudo apt dist-upgrade -y, create a user, give the user sudo privs and then run the curl to bash installer .

Or you could just try running axiom-build default and showing me the output and maybe we can see whats going on, the former suggestions are more likely to work however.

0xtavian commented 2 years ago

@Sicks3c gong to close this issue as i am not able to reproduce. feel free to comment if u have an update