- Community Home
- >
- Servers and Operating Systems
- >
- HPE ProLiant
- >
- Server Management - Remote Server Management
- >
- Directory Server Name cannot be resolved - AD Auth...
Server Management - Remote Server Management
1753974
Members
7058
Online
108811
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-06-2009 08:21 AM
10-06-2009 08:21 AM
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?
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?
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP