peter@ficc.ferranti.com (Peter da Silva) (05/21/91)
Hi folks. I'm diving into the TCP/IP part of our network again. This time I want to set up a single nameserver machine, so we don't have to edit everyone's hosts.txt file for every new machine. Where do I look to find out how this is done? I want to use a System V/386 machine with intel's TCP/IP product as the nameserver if possible, but we will have a bunch of machines on it... including some Unisys 1100s that only support the basic DDN suite. Any hope of getting them to use a nameserver? Also, I'd like to use this as an opportunity to renumber our net. We originally set up as a class C network, but since we're unlikely to ever hook up straight to the real Internet is there any reason not to simplify things by using a class A network number? "Consult your local GURU", you say? Sorry, as far as this goes I'm as much of a GURU as anyone at this site. Pitiful, isn't it? To minimize bandwidth, please mail responses. -- Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180; Sugar Land, TX 77487-5012; `-_-' "Have you hugged your wolf, today?"
JRJONES@ALEX.STKATE.EDU (05/22/91)
> Also, I'd like to use this as an opportunity to renumber our net. We > originally set up as a class C network, but since we're unlikely to ever > hook up straight to the real Internet is there any reason not to simplify > things by using a class A network number? Yes but you may hook up to a real internet, say 2 years, 1 year or 5 years down the road. You wish you had applied to the network gods and got real numbers. I would recommend, that you apply for valid numbers so that you do not have to renumber some time in the future. It only takes a few minutes and fill in the blanks, to save a lot of hassle down the road. If you are the real GURU for your site I would recommend that you get Douglas Comer book on Networking it should help you understand some basics. jim jones College of St. Catherine jrjones@alex.stkate.edu 612-690-6856
dave@fps.com (Dave Smith) (05/23/91)
In article <70ECA8FF2AFF405D34@alex.stkate.edu> JRJONES@ALEX.STKATE.EDU writes: >> Also, I'd like to use this as an opportunity to renumber our net. We >> originally set up as a class C network, but since we're unlikely to ever >> hook up straight to the real Internet is there any reason not to simplify >> things by using a class A network number? > >Yes but you may hook up to a real internet, say 2 years, 1 year or 5 years >down the road. You wish you had applied to the network gods and got real >numbers. I will wholeheartedly second this having just spent my weekend renumbering FPS San Diego's network. Do it right the first time. It's much easier. -- David L. Smith FPS Computing, San Diego ucsd!celit!dave or dave@fps.com "It was time to stop playing games. It was time to put on funny hats and eat ice cream. Froggie played his oboe" - Richard Scarry
bob@MorningStar.Com (Bob Sutterfield) (05/23/91)
...since we're unlikely to ever hook up straight to the real
Internet is there any reason not to simplify things by using
a class A network number?
Yes but you may hook up to a real internet, say 2 years, 1 year
or 5 years down the road. You wish you had applied to the
network gods and got real numbers.
I have helped several organizations prepare for and achieve Internet
connectivity, none of whom thought they'd ever have it when they first
"designed" (I use that term loosely :-) their local network and
connected those first two workstations to a little hunk of yellow
Ethernet. Now that they have dozens or hundreds of machines talking
IP, it's exponentially more difficult to renumber than it would have
been if they had started with their own address in the first place.
How many networks have you seen numbered 192.9.200? Sun did the world
a favor by introducing them to IP, but didn't emphasize the need to
acquire their own slice of the address space. One very large local
organization has been using 192.9.200, ..201, ..202, ..203, and ..204
for years. Now it has become an issue of turf battles and intense
internal politics, as they must renumber all those hosts and gateways.
The transition from isolation to "connected status" is turning out to
be far, far more painful than it needed to be.
Do it right the first time. It's much easier.
Amen.jonson@SERVER.AF.MIL (Lt. Matt Jonson) (06/04/91)
<Peter da Silva writes> > Subject: Diving into TCP/IP again... need help finding docco... > Message-Id: <COGBBWG@xds13.ferranti.com> > > machines on it... including some Unisys 1100s that only support the basic > DDN suite. Any hope of getting them to use a nameserver? > The trick in the AF (we have a bunch of 1100s, which, in some cases act as "e-mail hosts") is to use the nameserver as a forwarding agent. The 1100 style mail will use a header like 131-16-2-1::mailbox which tells it to send to mailbox@131.16.2.1. If you know a hostname, bounce the mail off a host that knows how to resolve hostnames, e.g. your nameserver host. Let's say your nameserver host is 192.30.100.1 and you had Internet connectivity and want to send to me from the 1100. Cheat and do this: 192-30-100-1::jonson@server.af.mil Not pretty, but it will work. If you have any more in depth questions about 1100s, I can put you in touch with the AF Gurus. I generally avoid those machines because they are about as friendly as holding a snake in the hand. /matt -- Lt Matthew W Jonson jonson@server.af.mil snail-mail: Network Systems Engineer 205-279-4075 SSC/SSMT USAF DDN Program Office AV: 596-4075 Gunter AFB, AL 36114 Any opinions herein are my own, and do not represent official AF views.