Incorrect IP selection from resolved hostname when multiple IPs are returned by NS

[scmanjarrez]

Hi,
First of all, thank you very much for your tool. I recently encountered an error with bloodhound-python, which happened during an HTB machine. However, I believe this issue might be more common:

When a hostname resolves to multiple IPs, bloodhound-python only chooses the last one instead of testing connectivity with all the resolved IPs. This behavior can be seen here: https://github.com/dirkjanm/BloodHound.py/blob/bloodhound-ce/bloodhound/ad/domain.py#L67

I currently have a workaround, but I think a cleaner solution could be implemented.

# Imports
import ldap3
# <SNIP>
        for r in q:
            try:
                logging.info('Testing resolved hostname connectivity %s' % r.address)
                _tmp_serv = ldap3.Server(r.address, connect_timeout=5)
                _conn = ldap3.Connection(_tmp_serv)
                _bind = _conn.bind()
            except ldap3.core.exceptions.LDAPSocketOpenError:
                continue
            else:
                if _conn:
                    ip = r.address
                    break