Skip to content

Commit 215b4a1

Browse files
committed
Fix DNS resolver thread counts in tips and tricks
1 parent 0ab5e54 commit 215b4a1

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

docs/scanning/tips_and_tricks.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -47,15 +47,15 @@ bbot -t evilcorp.com -f subdomain-enum -c dns.brute_threads=5000
4747

4848
### Speed Up Scans with More DNS Resolvers
4949

50-
By far the most effective way to speed up a BBOT scan is to **add more resolvers to `/etc/resolv.conf`**. BBOT's DNS engine (blastdns) spins up ten workers per resolver, so more resolvers = more parallelism = faster scans.
50+
By far the most effective way to speed up a BBOT scan is to **add more resolvers to `/etc/resolv.conf`**. BBOT's DNS resolver (blastdns) spins up multiple threads per resolver (default: `5`, configurable via `dns.threads`), so more resolvers = more parallelism = faster scans.
5151

5252
For OSINT, it's critical that every resolver is **unfiltered**. Specialized resolvers that try to block ads, malicious domains, etc. will intentionally omit results. Below is a sample `/etc/resolv.conf` with 11 unfiltered public resolvers:
5353

5454
```conf
5555
--8<-- "docs/data/resolv-sample.conf"
5656
```
5757

58-
Copy this to `/etc/resolv.conf` (or append the `nameserver` lines to your existing config). With all 11 resolvers, blastdns will run 110 workers in parallel instead of the typical 10-30 you get from a default OS config.
58+
Copy this to `/etc/resolv.conf` (or append the `nameserver` lines to your existing config). With all 11 resolvers at the default 5 threads each, blastdns will run 55 workers in parallel instead of the typical 5-15 you get from a default OS config.
5959

6060
!!! tip
6161
If your system uses `systemd-resolved` or `resolvconf`, you may need to configure the upstream forwarders there instead of editing `/etc/resolv.conf` directly.

0 commit comments

Comments
 (0)