bitbrute / bitbrute/evillimiter-windows
Resolving hostnames takes too long
Open
enhancement
- Dominant language
- C#
- Stars
- 233
- Forks
- 36
- PR merge metrics
- No merged PRs in 30d
Description
I'm in a network that has about 100-200 people in it, and resolving the hostnames takes too long. I don't really need the names so would there be an option to skip it (or a timeout perhaps?)
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points. Start by locating where hostname resolution occurs, then determine how the existing network-monitoring flow handles its result. Done means users can skip hostname resolution or configure a timeout so monitoring is not delayed when names are unnecessary.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100