DNS resolution error

Open
#203 2 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Quiet
Tech stack
csharp
Domain
networking, security

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.

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

Dominant language
C#
Stars
1.3k
Forks
266
Avg merge
2d 7h
Merged PRs (30d)
3

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from SpecterOps/SharpHound

All issues in SpecterOps/SharpHound

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.