https://community.hpe.com/t5/server-management-remote-server/directory-server-name-cannot-be-resolved-ad-auth-fails/m-p/4508830#M4707 We have recently added / decommisioned some AD servers in our environment and we are in the process of changing our iLo settings to match. When we change the Directory Server Address on the Directory tab and run the tests they fail right away with the following errors:<BR /><BR />Directory Server DNS Name Failed <BR />Unable to resolve host name<BR /><BR />We have not changed the DNS server that these cards connect to for name resolution and the records do exist and are resolvable from other systems in the environment.<BR /><BR />The common thread seems to be that if the hostname begins with a number that the resolution fails. If we change the Directory Server Address to a name in our DNS server that begins with a non-numeric charcter name resolution works. Of course, all our machines are moving to a naming convention that begins with a number, as we haven't had any other systems exhibit this name resolution issue.<BR /><BR />Are there any known issues where these cards cannot resolve hostnames that begin with a number?<BR /><BR /> Tue, 06 Oct 2009 15:21:27 GMT Mike DiBenedetto 2009-10-06T15:21:27Z https://community.hpe.com/t5/server-management-remote-server/directory-server-name-cannot-be-resolved-ad-auth-fails/m-p/4508830#M4707 We have recently added / decommisioned some AD servers in our environment and we are in the process of changing our iLo settings to match. When we change the Directory Server Address on the Directory tab and run the tests they fail right away with the following errors:<BR /><BR />Directory Server DNS Name Failed <BR />Unable to resolve host name<BR /><BR />We have not changed the DNS server that these cards connect to for name resolution and the records do exist and are resolvable from other systems in the environment.<BR /><BR />The common thread seems to be that if the hostname begins with a number that the resolution fails. If we change the Directory Server Address to a name in our DNS server that begins with a non-numeric charcter name resolution works. Of course, all our machines are moving to a naming convention that begins with a number, as we haven't had any other systems exhibit this name resolution issue.<BR /><BR />Are there any known issues where these cards cannot resolve hostnames that begin with a number?<BR /><BR /> Tue, 06 Oct 2009 15:21:27 GMT https://community.hpe.com/t5/server-management-remote-server/directory-server-name-cannot-be-resolved-ad-auth-fails/m-p/4508830#M4707 Mike DiBenedetto 2009-10-06T15:21:27Z