search

owasp-amass / amass

In-depth attack surface mapping and asset discovery
https://owasp.org/www-project-amass/
Other
11.82k stars 1.87k forks source link

Amass ignoring config maximum_dns_queries #510

Open rjenningsuk opened 3 years ago

rjenningsuk commented 3 years ago

I noted this on a closed task but thought I'd create a new one. I've recently been having big issues with amass taking forever to complete tasks and it kept firing loads of requests with very high 80% retry as if the leaky bucket wasn't working or atleast very very slowly. This ended up with amass tasks sometimes taking hours to complete.

I had a maximum_dns_queries limit set to 250 in the config but it was still firing 1500+ req/sec. I moved from setting the maximum_dns_queries setting in a config file to the cli and now it works all the time everytime.

Thought it was worth mentioning as it's probably a simple fix / oversight.

caffix commented 3 years ago

This is somewhat complicated since many resolvers are being used at the same time, some trusted and other untrusted, all changing the rate of request per second based on resolver response rate