[723] in SIPB_Linux_Development
Re: BIND 4.9.3-BETA9
daemon@ATHENA.MIT.EDU (Salvatore Valente)
Tue Sep 27 22:30:53 1994
Date: Tue, 27 Sep 1994 22:30:41 -0400
To: Derek Atkins <warlord@MIT.EDU>
Cc: linux-dev@MIT.EDU
In-Reply-To: [721]
From: Salvatore Valente <svalente@MIT.EDU>
Hello.
I wanted to know if people had any problems with:
1) Me installing (and testing) BIND 4.9.3 on quiche, and
Do it.
2) Me creating a named package for Linux which would include
the programs from the bind installation as well as the MIT default
named config files, so that people can run named locally for better
name-service performance.
Don't do it. named is a standard network program. Every distribution
that I've ever seen comes with it. There's no reason for us to
duplicate it in a linux-athena package. It's not linux-athena
specific, even a little.
I guess if this version is significantly newer / better than whatever
version comes with Slackware 2.0, you can package it and announce
"there's a newer version of named available". But I don't see any
real reason to do this. Lots of software has newer versions than the
last Slackware / Debian / whatever release contained. It's not
"linux-dev"'s concern.
As far as using named.mit and "nameserver 127.0.0.1": of course it's
the Right Thing To Do. That's why every public cluster machine does
it. That's why quiche has been doing it for over a year. I'm sure
that lots of people using Linux-Athena had enough clue to set up their
system that way.
Something useful would be to make a package of just /etc/named.* and
documentation for beginners of how and why to use them.
As an aside, I've noticed much beter performance when running named
locally on my machine over a 14.4 modem
Wow. Caching improves performance. Alert the media. :-)
Have a nice day.
-Sal.
