[4235] in North American Network Operators' Group
Re: Work Work Work
daemon@ATHENA.MIT.EDU (Robert Elz)
Mon Sep 9 15:27:35 1996
To: Scott Stansbury <scotts@franklin.nysernet.ORG>
Cc: randy@PSG.COM (Randy Bush), bmanning@ISI.EDU (Bill Manning),
vixie@wisdom.home.vix.com (Paul A Vixie), nanog@merit.edu,
iepg@iepg.org, namedroppers <namedroppers@INTERNIC.NET>
In-Reply-To: Your message of "Mon, 09 Sep 1996 10:42:02 -0400."
<199609091442.KAA20704@franklin.nysernet.ORG>
Date: Tue, 10 Sep 1996 05:21:02 +1000
From: Robert Elz <kre@munnari.OZ.AU>
Date: Mon, 09 Sep 1996 10:42:02 -0400
From: Scott Stansbury <scotts@franklin.nysernet.ORG>
Message-ID: <199609091442.KAA20704@franklin.nysernet.ORG>
Unfortunately, this doesn't work now. Our name servers get tens of thousands
of hits a day for a former root, c.nyser.net, a machine that hasn't existed for
quite some time.
There's absolutely nothing you can do about those, they're the
result of old software with old configurations. Changing at the
end nodes is the only thing that will ever fix that problem.
Certainly changing the root nameserver addresses isn't going to
make any difference (unless you can somehow guarantee that none
of the old root addresses has any kind of nameserver sutting at it,
that at least would motivate the old end sites a little).
Given that the end nodes have to be updated to make things better,
it seems that the best solution is to motivate them to upgrade
the software (it isn't exactly a difficult task) so that the
problem of changing root addresses (and lots of others) mostly
goes away.
Magic stable root addresses isn't likely to be much of a long term
help, regardless of how well they can be propogated, or what kind
of message it sends wrt address & routing table slot conservation.
If anything, taht is likely to just encourage people to keep using
nameserver code that should have been retired years ago.
kre
