Simpler Navigation for Servers and Operating Systems - Please Update Your Bookmarks
Completed: a much simpler Servers and Operating Systems section of the Community. We combined many of the older boards, so you won't have to click through so many levels to get at the information you need. Check the consolidated boards here as many sub-forums are now single boards.
If you have bookmarked forums or discussion boards in Servers and Operating Systems, we suggest you check and update them as needed.
cancel
Showing results for 
Search instead for 
Did you mean: 

Resolving Without FQDN

Jonathan Lackey
Occasional Visitor

Resolving Without FQDN

I have a vendor application that does not allow enough space for a Fully qualified Domain Name (FQDN). This has caused my organization to do static entries in the /etc/hosts file for years. Is there a way to use dns and not append the domain name?

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?

4 REPLIES
TTr
Honored Contributor

Re: Resolving Without FQDN

Have you tried using DNS? You can still use the short name comp6 in the application and still resolve it using DNS. Your PC must be setup to use the "myorganization.com" as the default domain (DNS client).
Jonathan Lackey
Occasional Visitor

Re: Resolving Without FQDN

All of the resolution is on the UNIX box, the PCs (terminals) just point to the HPUX IP. The field in our application allows for around 12 characters in the resolved name. The DNS settings on the Unix box add the search field for our domain so that you can type in the short name. The problem is that it still returns the FQDN. Is the default domain name something that can be set on the UNIX host itself?
TTr
Honored Contributor

Re: Resolving Without FQDN

The default domain should be set in the /etc/resolv.conf file

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?
Steven E. Protter
Exalted Contributor

Re: Resolving Without FQDN

Shalom,

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
Steven E Protter
Owner of ISN Corporation
http://isnamerica.com
http://hpuxconsulting.com
Sponsor: http://hpux.ws
Twitter: http://twitter.com/hpuxlinux
Founder http://newdatacloud.com