Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uunet!bu.edu!buita!tower
From: tower@buita.bu.edu (Leonard H. Tower Jr.)
Newsgroups: comp.org.usenix
Subject: Re: Anaheim Terminal Room Update
Summary: cute, Bob, cute ;-}
Message-ID: <58446@bu.edu.bu.edu>
Date: 7 Jun 90 19:51:13 GMT
References: <371@usenix.ORG> <BOB.90Jun7143832@volitans.MorningStar.Com>
Sender: news@bu.edu.bu.edu
Reply-To: tower@buita.UUCP (Leonard H. Tower Jr.)
Organization: ~/.mail-plain.cf
Lines: 22

In article <BOB.90Jun7143832@volitans.MorningStar.Com> bob@MorningStar.Com (Bob Sutterfield) writes:
|In article <371@usenix.ORG> sonya@usenix.ORG (Sonya Neufer) writes:
|   ... NCD terminals ... a Xylogics terminal server ...
|   WRITE DOWN YOUR SYSTEM's INTERNET NUMBER and carry it with you, if
|   you plan to log in over the Internet.
|
|Those boxes don't resolve domain names?  How quaint!

The Terminal Room has had working DNS resolvers in the past.  I expect
it will this time.  

But bringing your SYSTEM's INTERNET NUMBER is still wise advice.
Practically, terminal room users have been able to telnet to their
home hosts with it's Internet number, at times when its Internet DNS
name has not been resolvable.  

To understand why, I suggest you study the relevant specs, figure out
likely failure modes, and try to run an operation like the Terminal
Room, or a Conference Show net to really gain an understanding of
likely failure modes.

thanx -len (a very happy Terminal Room user)