Windows2000 is a Noisy Neighbor.

Martin McCormick martin at dc.cis.okstate.edu
Mon Nov 13 17:35:10 UTC 2000


	Well, after one month and a twelve-meg log file, most of
which is occupied by:

13-Nov-2000 17:10:31.180 unapproved update from [139.78.xxx.xxx]

	I have the big shears out.  There is a category in the
example named.conf file called *update so I added a line to
named.conf as follows:

 category update	{ null; };	// don't log these at all

	There is supposed to be a blank preceding category, I
think, but this line has had no effect on the deluge.  I would
rather just let the Windows systems jabber their little hearts
out and ignore the traffic than try to police 20,000 addresses
and beg them not to run the updates, please!  Many people will
cooperate, but many more bring their new Windows 2000 systems up
each day and this is eating our disk space more than it is
hurting the network.

	It is truly amazing that a commercial software company is
that irresponsible to release a product that is defaulted to be
totally obnoxious on the network.  If one of our students did
this, he would be dealt with in much the same way we deal with
the kids who have written programs that have crashed UNIX systems
by spawning endless new processes until they run out.

	Oh well, I'm talking about the same geniuses who design
mailers that execute any old code that comes in from any old
place.  What can I say?

Martin McCormick WB5AGZ  Stillwater, OK 
OSU Center for Computing and Information Services Data Communications Group



More information about the bind-users mailing list