HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - Linux
- >
- Problem With Hostname Resolving
Operating System - Linux
1828207
Members
2235
Online
109975
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
Forums
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
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
07-24-2003 01:51 AM
07-24-2003 01:51 AM
Problem With Hostname Resolving
Hi,
We have a linux machine with proper network configuration. nslookup is working ok when you try to resolve other hostnames. But ping fails unless otherwise you give a FQDN.
i.e
ping node1 - fails
ping node1.domain.com - passes
What could be the reason. Problem is not only with the ping but due to this automounting of shares also fails. Extract from messages file,
-----------------------------------------------
[root@linux-pc /etc]# more /var/log/messages
Jul 20 04:25:17 linux-pc syslogd 1.4-0: restart.
Jul 20 04:24:55 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:25:54 linux-pc last message repeated 6 times
Jul 20 04:25:55 linux-pc automount[691]: attempting to mount entry /auto/ecs
Jul 20 04:26:04 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:26:05 linux-pc automount[9274]: mount(nfs): entry ecs: host coffee: lookup failure
Jul 20 04:26:14 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
-----------------------------------------------
Though it says NIS server is not reachable I am able to resolve other tables like passwd, group. DNS is used for hosts. /etc/resolv.conf and /etc/nsswitch.conf are just fine.
Pl. help
Thanks
Karthik S S
We have a linux machine with proper network configuration. nslookup is working ok when you try to resolve other hostnames. But ping fails unless otherwise you give a FQDN.
i.e
ping node1 - fails
ping node1.domain.com - passes
What could be the reason. Problem is not only with the ping but due to this automounting of shares also fails. Extract from messages file,
-----------------------------------------------
[root@linux-pc /etc]# more /var/log/messages
Jul 20 04:25:17 linux-pc syslogd 1.4-0: restart.
Jul 20 04:24:55 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:25:54 linux-pc last message repeated 6 times
Jul 20 04:25:55 linux-pc automount[691]: attempting to mount entry /auto/ecs
Jul 20 04:26:04 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
Jul 20 04:26:05 linux-pc automount[9274]: mount(nfs): entry ecs: host coffee: lookup failure
Jul 20 04:26:14 linux-pc nis_cachemgr[571]: Could not lookup cbin.eng.: NIS+ servers unreachable
-----------------------------------------------
Though it says NIS server is not reachable I am able to resolve other tables like passwd, group. DNS is used for hosts. /etc/resolv.conf and /etc/nsswitch.conf are just fine.
Pl. help
Thanks
Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
1 REPLY 1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-24-2003 02:12 AM
07-24-2003 02:12 AM
Re: Problem With Hostname Resolving
It is working now after a reboot.
Thanks for not replying :-)
-Karthik S S
Thanks for not replying :-)
-Karthik S S
For a list of all the ways technology has failed to improve the quality of life, please press three. - Alice Kahn
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.
Company
Support
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP