Hello John!

10 Apr 15 18:12, you wrote to me:

 JG> ->  I do not know how the NC's of those nodes determin if this are active
 JG> systems, ->  but it is certainly not by regular connects.

 JG> ->  This can be extended to RC's and ZC's as among the above groups are
 JG> ->  nethosts and region hosts.

 JG>     Not to be stepping on the toes of my NC, or my RC, but the policy4
 JG> does mention not wearing too many hats.  If a NC is a RC, then it can be
 JG> time consuming to check on each and ever node in his segment as well as
 JG> checking on things in his region...  Possibly a reason why at least some
 JG> RC's and ZC's don't do their job and mark nodes as being down...

 When was the last time you looked at the nodelist.

 The administration of the nodelist is a layered system. NC's administer
 nodes. RC's administer Nets. ZC'c administer Regions.

 Where RC's are NC's the nets only have a few nodes.

 The only region with nets of significant size is Region 50. There some nets
are large as at least 2 zones and possibly 3.

 There is a 4 Region zone smaller thena most nets, where two regions are
defunct.

 There are entries inn the nodelist that have expired in DNS when dyndns
 stopped their free service. That is more tha 1 year ago. If a NC is that far
 behind in his adminitration, lack of time can not be an exuse, that is
 total negligence.

 Some of these overworked RC's have plenty of time for useless discussions
 in these echo's

Kees

--- GoldED+/LNX 1.1.5