- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Resolving Without 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
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-06-2010 09:14 AM
тАО04-06-2010 09:14 AM
Resolving Without FQDN
E.G.
Our application is looking for a pc named comp6.
DNS resolves comp6.myorganization.com
Hosts resolves comp6 because we are not adding .myorganization.com behind it.
The application considers comp6 to be different than comp6.myorganization.com.
Can anyone help?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 09:24 AM
тАО04-06-2010 09:24 AM
Re: Resolving Without FQDN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 09:31 AM
тАО04-06-2010 09:31 AM
Re: Resolving Without FQDN
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 10:10 AM
тАО04-06-2010 10:10 AM
Re: Resolving Without FQDN
domain myorganization.com
What does your application expect from the name resolution?
DNS will send back the FQDN and the IP address. If your app checks the name as well as the IP, the lookup will fail.
Maybe your application has a default domain somewhere in its configuration?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО04-06-2010 11:11 AM
тАО04-06-2010 11:11 AM
Re: Resolving Without FQDN
DNS provided by Microsoft servers will resolve names by short name (not fdqn) if the Microsoft DNS servers are configured to do this.
This will work for systems running winbind, but can at the DNS server level be configured for all system types. You can with CIFS/9000 run winbind on your HP-UX system anyway.
There are limits to short name resolution, based on Microsoft domain name.
For simple situations though, simple /etc/hosts resolution might suffice for short names. Simply configure /etc/nsswitch.conf to look to files first
and then set up /etc/hosts
ipaddress fdqn shortname
192.168.0.10 server.example.com server
SEP
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com