From: mhuth@byron.u.washington.edu (Mark Huth)
Newsgroups: comp.os.os2.networking
Subject: Re: Using my local nameserver
Date: 5 Nov 92 07:05:19 GMT
Article-I.D.: u.1992Nov5.070519.3166
Organization: University of Washington, Seattle

In article <1992Nov04.192809.23591@ans.net> db3l@ans.net (David Bolen) writes:
>In article <1992Nov3.205131.18519@u.washington.edu> mhuth@byron.u.washington.edu (Mark Huth) writes:
>
>>I'd like to make use of the local nameserver from tcp/ip package for os/2.  I
>>presume that I need to specify the ip addresses for that nameserver in my 
>>resolv file.  However, what name should I specify for the domain in the
>>resolve file?  (or is there another way to do what I want to do??)  
>
>Well, that depends on what domain name you want to assume in requests that
>you make to the nameserver.  Whatever you put in the resolv file will
>automatically get tacked on to any hostname you don't fully qualify,
>but beyond that it really doesn't matter much what you put there.
>
>For example, one of my work hosts is "istari.ans.net", and we have a local
>nameserver.  I use "domain ans.net" and "nameserver 147.225.10.31" in my
>resolv.  However, my home SLIP host is "havens.slip.ans.net", but I
>use the same resolv file.  That's because although I'm in the
>"slip.ans.net" domain at home, just about everything I access by name
>is in the "ans.net" domain, so that's more logical to put in resolv.
>
>I could just as easily put in "domain cmu.edu", and then I could refer
>to CMU hosts without qualifying them, but I'd have to qualify .ans.net
>hosts.
>
>So it's your choice, but the normal way is to put in your local
>domain, since you are most likely to refer to local machines without
>using their fully-qualified name.
>
>--
>-- David
>--
>/-----------------------------------------------------------------------\
> \              David Bolen             \  Internet: db3l@ans.net      /
>  |   Advanced Network & Services, Inc.   \   Phone: (914) 789-5327   |
> / 100 Clearbrook Road, Elmsford, NY 10523  \   Fax: (914) 789-5310    \
>\-----------------------------------------------------------------------/

David, your explaination is quite clear.  My problem however is that TCP/IP
isn't finding the global nameservers.  For example, lets say I want to telnet
from my pc to an account at Yale.  Whenever I attempt to do this, I get an error
which tells me that the network isn't accessible (or words to that effect!). 
If I log onto one of the university machines and attempt to make the same
telnet connection....it connects right away.  My assumption was that by 
putting the local global nameservers in the resolv file, TCP/IP would make use
of the global nameservers and enable me to telnet (or send mail) to distant 
sites.  
My resolv file is setup as follows:

Domain u.washington.edu
nameserver 123.456.789.x
nameserver 123.456.789.y

Any clues why this doesn't work?

On another matter, every time I exit the Xwindows server I get a system crash
...one of those horrible errors like location x67895...contact your service 
representive.  This started occuring after I installed the service pack.  
Doesn't give me a warm feeling about the stability of the Xwindows package!
-- 
Mark Huth                         * Office 206-543-3429 
Mhuth@u.washington.edu            * Fax    206-685-9394
Compuserve 70346,563              *
Newsgroups: comp.os.os2.networking