HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Server Management - Remote Server Management
Showing results for 
Search instead for 
Did you mean: 

Directory Server Name cannot be resolved - AD Auth fails

Mike DiBenedetto
Occasional Visitor

Directory Server Name cannot be resolved - AD Auth fails

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:

Directory Server DNS Name Failed
Unable to resolve host name

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.

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.

Are there any known issues where these cards cannot resolve hostnames that begin with a number?