Path: utzoo!attcan!uunet!samsung!usc!ucsd!ucbvax!ucsfcgl!cca.ucsf.edu!wet!stan
From: stan@wet.UUCP (Stan Osborne)
Newsgroups: comp.sys.apollo
Subject: /etc/resolv.conf help needed
Summary: name resolution not working
Message-ID: <1504@wet.UUCP>
Date: 6 Sep 90 06:49:24 GMT
Reply-To: stan@cs.sfsu.edu (Stan Osborne)
Organization: San Francisco State University
Lines: 38

We just installed our first SR10.2 on a DN 2500 (Ethernet Device).
(This is actually running SR10.2.1.1, the specail DN2500 update.)
This is our only Domain System.  We are considering getting more.

/etc/resolv.conf was created as described in "Configuring and 
Managing TCP/IP (008543-A02)" page 3-7,3-8. The name server daemon 
is not running on the DN2500.  With "nmconfig -h hostent_ascii"
names in /etc/host work ok.  With "nmconfig -h hostent_bind" names
in /etc/host do not work.  In either case names not in /etc/host
are not resolved.  If the literal IP number is used instead of
a name, things work as expected.  With "nmconfig -h hostent_bind" 
enabled, some programs (like telnet) get a "Segmentation" error
when a fullly qualified name is used (e.g. cs.sfsu.edu vs cs).

We have looked all over the documentation and man pages.  There is no 
other reference to the correct use of /etc/resolv.conf besides the 
above mentioned pages.

We don't need a complete /etc/hosts on any of our other IP machines
(Suns, NeXTs, Macs, PCs, etc.).   We don't want to run named or build
a complete /etc/host on the DN2500.

Is there a way to get this to work?
Is this a known bug?
Is there a patch or work around?
Should we submit an apr?

In a few hours I will contact our local support person.  I don't expect
a response as timely as is likely from the friendly folk reading
comp.sys.apollo.  

Please email replies even if you post a followup.
Thanks.

Stan Osborne
stan@cs.sfsu.edu
Computer Science Dept.
San Francisco State University