North American Network Operators Group

Date Prev | Date Next | Date Index | Thread Index | Author Index | Historical

Re: Work Work Work

  • From: Robert Elz
  • Date: Mon Sep 09 15:26:30 1996

    Date:        Mon, 09 Sep 1996 10:42:02 -0400
    From:        Scott Stansbury <[email protected]>
    Message-ID:  <[email protected]>

    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
- - - - - - - - - - - - - - - - -