It looks like the AD setup-up at my company returns a "." character at the and
of the _ldap._tcp SRV record for the AD domain. When Hudson tries to access the
LDAP using such a host name, it of course fails because it can't resolve the
hostname. The following patch will deal with the issue by replacing any for
chars at the end of the hostname parsed from SRV record.