Skip to content

Conversation

@Luesewr
Copy link
Contributor

@Luesewr Luesewr commented Jul 11, 2025

A fix to significantly reduce the amount of DNS Timeout messages.

I was testing out the tool and noticed that for any input I gave it, the DNS requests always had timeouts at random websites, such as this:
image
There seemed to be no consistency across multiple scans of the same input, so I assumed it was a DNS rate limiting issue (which seems to be correct). This fix gets around the rate limiting issue by modifying the dns_lookup method in utils, such that it retries a maximum of 3 times when encountering DNS timeouts. In my experience, this also allows the timeout limit to be reduced to 3 seconds instead of 10 without any impact on the accuracy. I could consider changing the timeout limit back to account for worse hardware/DNS connections, but it could also be added as a command line argument if need be.

So far it has given me no more DNS timeouts and should slightly increase the performance of the DNS sections of the scanner and the accuracy, since before it wasn't retrying the timed-out websites, so they weren't properly tested.

@initstring
Copy link
Owner

Thanks @Luesewr - looks like a neat solution with no negative impact. Will merge it now. Appreciate your contribution!

@initstring initstring merged commit 13fefdb into initstring:master Jul 12, 2025
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants