Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!att!ucbvax!YALEMED.BITNET!BEEBE
From: BEEBE@YALEMED.BITNET (Rick Beebe)
Newsgroups: comp.protocols.tcp-ip.ibmpc
Subject: Re: ka9q configuration
Message-ID: <A6B83551600009C4@YALEMED.BITNET>
Date: 19 Apr 91 13:12:00 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 40

>[...]
>I built the following autoexec.nos in the root directory:
>
>[...]
># incorporate the local nameserver for lookups
>#
>domain addserver [128.48.100.91]  #nile
>[...]
>Q: can 1 use the names autoexec.nos and autoexec.net interchangeably ??
>
>The problem is I have to give the IP adresses, when I am ftp'ing.
>What do I have to do to be able to use names instead of IP adresses ??

There are two versions of the KA9Q software out there. The original was called
NET and used autoexec.net. Sometime around 1989, Phil Karn completely rewrote
it and renamed it NOS. Obviously, one uses autoexec.net the other autoexec.nos.
Unfortunately, to add the to the confusion, oft-times I see copies of NOS that
are named NET.EXE. Very bewildering, although it does display the name
correctly when you fire it up. You can pass the name of the configuration file
on the command line, so if your heart is set on using autoexec.net, just call
it like this: NOS AUTOEXEC.NET.

The line in your autoexec.nos (included above) "domain addserver" adds the ip
address of your local name server. That should be all you need to be able to
use names. When you open a connection using a name, NOS will send a query to
128.48.100.91 to resolve that name. If it's not working, then you need to talk
to your local net gurus to see why. When NOS has resolved a name, it will put
it in a file on your disk called domains.txt (called a local cache) so that
subsequent connects to that node will be much faster.


-----------------------------------------------------------------------------
                                Rick Beebe                    (203) 785-4566
 *****  *****  *****  *   *     Biomedical Computing Unit
   *      *    *      **  *     Yale University School of Medicine
   *      *    ***    * * *     333 Cedar Street, New Haven, CT 06514
   *      *    *      *  **
   *      *    *      *   *     BEEBE@YALEMED.BITNET
                                beebe@biomed.med.yale.edu
-----------------------------------------------------------------------------