Fix to solve DNS resolution fail when different DNs sufix #196
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I faced some issue when using a BloodHound in a environment with a different DNS sufix.
Error sample 1
Error sample 2
This second error show me what is the issue
Looking at my DNS config
ccat /etc/resolv.conf ───────┬──────────────────────────────── │ File: /etc/resolv.conf ───────┼──────────────────────────────── 1 │ # Generated by NetworkManager 2 │ search labpentestbrasil.com.br 3 │ nameserver 192.168.30.1 ───────┴────────────────────────────────
Solution PoC
To test i just put the "." at the end of the domain
Solution
Add the following code to force "." at the end
Final test