Open n3rada opened 4 months ago
I have found something. I need to put in my /etc/resolv.conf
first dc as the name server and add @home.com
to the username and it will work. That solves the problem:
nslookup rdc02.dev.com 172.16.186.168
Server: 172.16.186.168
Address: 172.16.186.168#53
Non-authoritative answer:
Name: rdc02.dev.com
Address: 172.16.186.160
In an environment where DMZDC01.HOME.COM has a trust relationship like this:
It is possible to retrieve all
dev.com
data from thedc01
while runningSharpHound
:But with
bloodhoun-python
it fails:Using
klist
afterSharpHound
execution result in created tickets:Maybe
bloodhound.py
needs to forge the same tickets.