[34253] in North American Network Operators' Group
Reasons why BIND isn't being upgraded
daemon@ATHENA.MIT.EDU (Jason Lewis)
Thu Feb 1 02:03:47 2001
Reply-To: <jlewis@jasonlewis.net>
From: "Jason Lewis" <jlewis@jasonlewis.net>
To: "'nanog'" <nanog@merit.edu>
Date: Thu, 1 Feb 2001 02:00:51 -0500
Message-ID: <004f01c08c1c$b6eafbc0$4d14a8c0@jasonlewis.net>
MIME-Version: 1.0
Content-Type: text/plain;
charset="us-ascii"
Content-Transfer-Encoding: 7bit
In-Reply-To: <Pine.BSF.4.30.0102010131420.16165-100000@shell.inch.com>
Errors-To: owner-nanog-outgoing@merit.edu
All of the recent list traffic got me thinking about why people aren't
upgrading. Maybe some insight?
I have several name servers. I have inherited them from admins that didn't
seem to know what they were doing and I cannot upgrade one of them at all.
It would require a total rebuild. I have upgraded the rest to 8.2.3.
Another reason I haven't put more effort into it, is because I am waiting
for two brand spanking new servers to arrive. I don't have the time to
rebuild a name server I will trash in less than a week. Russian Roulette, I
know.
Is it pretty common to be understaffed and overworked? I can't believe I
just asked that. I am always overworked with next to no help, but it seems
that recently things are worse. Is that true all around?
Anyone else in similar situations?
Also, anyone else see a HUGE increase in scans for port 53? I mean out of
control scans.
jas
