- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - OpenVMS
- >
- Lookup failure
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
Forums
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
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
тАО04-27-2006 09:06 PM
тАО04-27-2006 09:06 PM
The command $ TCPIP SHO HOST 3.3.3.3 gives me from the bind server a nodename, so this works as it should work.
The command $ TCPIP SHO HOST
What is wrong?
Greetings,
Piet Timmers
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2006 09:29 PM
тАО04-27-2006 09:29 PM
Re: Lookup failure
perhaps something with your default domain or the path of the nameserver?
regards Kalle
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2006 09:34 PM
тАО04-27-2006 09:34 PM
Re: Lookup failure
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2006 09:36 PM
тАО04-27-2006 09:36 PM
Re: Lookup failure
TCPIP SHOW NAME
Purely Personal Opinion
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-27-2006 11:37 PM
тАО04-27-2006 11:37 PM
Solution- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-28-2006 01:25 AM
тАО04-28-2006 01:25 AM
Re: Lookup failure
Call me "Old Fashioned", but I generally use nslookup for DNS checks.
Jim is certainly correct, forward and reverse DNS are by no means guaranteed to be synchronized. In most (almost all) DNS implementations, these two are maintained separately (often by completely different organizations; the forward is maintained by the owner of the sub-domain to which the machine belongs, the reverse is maintained, by necessity, by the group responsible for actual physical network connections, rarely are these groups one and the same).
- Bob Gezelter, http://www.rlgsc.com