Linda,
Remember that nslookup does not look
at the /etc/hosts file, so it doesn't
really give the complete picture.
Try this: put a bogus entry in /etc/hosts
then do an nslookup on that entry (forward
and reverse) and notice that nslookup won't
find it.
However, the resolver will use /etc/hosts, and
if you have told the resolver (via /etc/resolv.conf)
to use /etc/hosts, then dns, then NetView is going
to do that and pick up reverse names from /etc/hosts
if they are in there. There is no nslookup type
program that queries /etc/hosts, I guess no one
thinks they need it since /etc/hosts is an ascii
file and grep will do fine.
So, if you have added host names into /etc/hosts
without the domain suffix, NetView will eventually
find and use them.
Les
>From: "Linda Parry" <lparry@MetLife.com>
>Reply-To: IBM NetView Discussion <nv-l@tkg.com>
>To: "IBM NetView Discussion" <nv-l@tkg.com>
>Subject: Re: [NV-L] Selection Name missing domain suffix
>Date: Thu, 28 Jun 2001 15:13:28 -0400
>
>
>Les, Thank you .. but I think something else is wrong. A ping does not
>use the fully qualified name. The nslookup command reponds with fully
>qualified names reverse and forward lookup. We do have a hosts file in
>/etc which we use to create the dns files (it has some aliases with fully
>qualified names). However... when I remove the hosts file (rename it to
>something else) then my ping will use the fully qualified name. The system
>is using the hosts file first then dns. It seems that the machine is not
>reading my resolv.conf file for whatever reason. We have not changed this
>file and it looks identical to another system we are running which is
>working fine. It seems like a DNS issue for the machine. NOT sure why
>this is happening. Short term I may just rename the HOSTS file.
>
>
>
>
>_________________________________________________________________________
>NV-L List information and Archives: http://www.tkg.com/nv-l
_________________________________________________________________
|