- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Not able to ping to FQDN
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Discussions
Forums
Discussions
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
Community
Resources
Forums
Blogs
- 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
11-04-2011 11:59 AM
11-04-2011 11:59 AM
Not able to ping to FQDN
Hi,
I have 1 solaris server inside that there are couple of zones.
When i am trying to ping to FQDN it is not working.
If i ping server directly by server name its going fine.
Could you please help me where i need to check.
Regards,
RC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2011 12:40 PM
11-04-2011 12:40 PM
Re: Not able to ping to FQDN
How are you resolving host names? Are you using DNS? What happens if you try to do an 'nslookup' ofr the FQDN?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-04-2011 12:50 PM
11-04-2011 12:50 PM
Re: Not able to ping to FQDN
Hi,
Thanks for reply. Nslookup is working fine.
It having issue when we ping FQDN.
Thanks,
RC
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
11-05-2011 02:15 AM
11-05-2011 02:15 AM
Re: Not able to ping to FQDN
The nslookup command can have different behavior in different unix-style OSs:
- In HP-UX, the standard nslookup command will look up both DNS and /etc/hosts, according to the settings in /etc/nsswitch.conf.
- In most modern Linux distributions, the nslookup command will always use DNS only. This means it may give different results than the regular applications get when resolving hostnames using a gethostbyname() system call.
- I wonder how Solaris behaves in this regard?
If you run nslookup with FQDN and get an IP address as a result, try pinging using that IP address. If the ping is successful, the problem is that the ping command cannot resolve the FQDN: check your /etc/nsswitch.conf and /etc/resolv.conf.
Note that IPv6-aware programs might use a different nsswitch.conf line than the IPv4-only programs. For example, in HP-UX 11.23 and newer, the hostname lookup of IPv4 programs is controlled by the "hosts:" line in /etc/nsswitch.conf, but IPv6-supporting programs use the "ipnodes:" line instead (for both IPv4 and IPv6 lookups!). I guess that a modern Solaris system might have IPv6 support included in commands like ping too.
If the ping with the IP address (from the FQDN nslookup) fails, then do another nslookup with the short name and see if it reports the same IP address. If the second nslookup produces a different IP address, check the "domain" or "search" lines in /etc/resolv.conf: perhaps the default domain suffix is not the one you expect.
Also check /etc/hosts: if it includes a line with the wrong IP address + FQDN, fix it.