You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I love the speed of this tool but I seem to get suprisingly inaccurate results. Could this be caused by rate limiting of the used resolver?
For subbrute (https://github.com/TheRook/subbrute) I use a list of DNS resolvers which works great. Would such a solution also be possible in dnsbrute?
Not familiar enough in go to implement this myself sadly..
The text was updated successfully, but these errors were encountered:
I've been able to confirm that rate limiting indeed seems to be the issue. Using dnsblast it's easy to determine what the rate limits of a dns resolver is.
I've written a easy shell script that tries 10000 queries @ 1000 qps and outputs the stats. This helps checking a list of resolvers and find one with the lowest rate limit. I've shared it below incase it might help someone.
Save the following as scan.sh:
#!/bin/bash
IP=$1
TIMEOUT=3 # Timeout scan (in seconds). Lower for faster results.
QUERIES=10000 # How many queries to send
QUERY_RATE=1000 # Queries per seconds
STATS=`timeout $TIMEOUT ~/misc/dnsblast/dnsblast $IP $QUERIES $QUERY_RATE 2>&1 | grep -E '^\S' | tail -n 1`
echo "$IP - $STATS"
Usage:
# Scan a single IP
$ ./scan.sh 8.8.8.8
# Check list of resolvers. Lower the amount of threads if you run out of buffer size.
$ cat resolvers.txt | parallel -j 4 './scan.sh {}'
I love the speed of this tool but I seem to get suprisingly inaccurate results. Could this be caused by rate limiting of the used resolver?
For subbrute (https://github.com/TheRook/subbrute) I use a list of DNS resolvers which works great. Would such a solution also be possible in dnsbrute?
Not familiar enough in go to implement this myself sadly..
The text was updated successfully, but these errors were encountered: