SpecterOps / SpecterOps/SharpHound
DNS resolution error
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1.3k
- Forks
- 266
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 3
Description
When used outside the domain, an error message "|ERROR|Unable to resolve a domain to use, manually specify one or check spelling" will be reported. This is likely a problem with DNS resolution. Could an additional parameter be added, such as specifying a DNS server, like -ns in BloodHound.py? Otherwise, it will be impossible to collect domain internal data outside the domain. thanks
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the DNS resolution path and the existing command-line parameter handling in SharpHound, then compare the requested behavior with BloodHound.py's -ns option. Done means a caller can specify a DNS server when running outside the domain and domain-internal collection no longer fails solely because automatic resolution cannot find a usable domain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- networking, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100