manager@a.coe.wvu.wvnet.edu (Cris Fuhrman, Systems Manager) (03/28/89)
Salut,
We have 3 Annex Terminal servers, connected via TCP/IP to our ethernet.
The problem concerns the handling of host names. Here's what happens:
After a server boots, one can access nodes outside of our local domain
(i.e. outside of .wvnet.edu). However, after a period of time, if one
tries to access even the same node as before, the address is resolved, and
the internet number is added to the cache hosts table, but the Annex
responds with (an immediate response, i.e. no delay)
Trying...
CLI: Network is unreachable.
As I said, the nameserver features appear to be working, and in fact our
ethernet is working, as I can telnet to remote hosts right after a boot.
Anyone have any input on this one?
Also, I have some related questions:
1) What's the difference between BIND, IEN_116, and RWOD name servers?
2) Are the RWOD machines the ones that show up in the hosts table with
a system load factor?
I have a couple of other minor questions about Annex configurations in
general, and I'd like to pick someone's brain about them if they'd be
willing to exchange some info.
-Cris
--
/''''--''''''''''''''''. Cris Fuhrman, Systems Manager''''''''''''''/
/ / \ . WVU College of Engineering /
< | __ o . Morgantown WV 26506-6101 <
\ | ) | | /\ . internet: manager@a.coe.wvu.wvnet.edu \
\...\___/...|_/|_/__).....bitnet:....manager%wvucoe@wvnvms...........\
Plus ca change, plus c'est la meme chose.ron@ron.rutgers.edu (Ron Natalie) (04/01/89)
RWHOD is a pretty lousy program in that each machine broadcasts it's users every 3-5 minutes. That Encore ever used that for getting name to address matching is an extreme kludge. They ought to be embarassed. Part of the rwho message is an indication of the system load and how long it's been up (as displayed by the ruptime command on UNIX). IEN-116 was the original name server, but it never really hit wide use. It is trivial to implement, and hence you can get it going on nearly anything that has UDP on it. BIND is the name of the Berkeley program that implements the IP Domain Name Service on UNIX. This is really what people ought to be using these days, and is really required if you are in a large network environment or are connected to the Internet at large.
prc@maxim.ERBE.SE (Robert Claeson) (04/04/89)
In article <Mar.31.13.10.21.1989.3524@ron.rutgers.edu>, ron@ron.rutgers.edu (Ron Natalie) writes: > BIND is the name of the Berkeley program that implements the IP > Domain Name Service on UNIX. This is really what people ought > to be using these days, and is really required if you are in a > large network environment or are connected to the Internet at large. Where can I find a good implementation of it for System V systems with sockets and/or TLI? -- Robert Claeson, ERBE DATA AB, P.O. Box 77, S-175 22 Jarfalla, Sweden Tel: +46 (0)758-202 50 Fax: +46 (0)758-197 20 EUnet: rclaeson@ERBE.SE uucp: {uunet,enea}!erbe.se!rclaeson ARPAnet: rclaeson%ERBE.SE@uunet.UU.NET BITNET: rclaeson@ERBE.SE