dmx

Thanks for the quick review! **What’s the actual root cause?** AD itself is healthy. The failure happens specifically in the *collector’s* DNS path: * The LDAP bind from NetExec to...

Another context of my environment: I'm testing on an AD hosted in a VM on Azure, so we have a local DNS: corp.local But, when nxc makes the requests, it...

Yes, my environment is really not the most ideal, nor the most organized; it's an AD WinServer 2016 that's most likely poorly configured lol. Using bloodhound-python, it managed to collect...

Yes, it might be a problem with bloodhound-python, but I used it and it worked fine; I didn't receive that NXDOMAIN error. So for me, the problem isn't with it.