Hello Bj”rn,
On Monday April 29 2019 11:10, you wrote to me:
BF> From zero to 13 6DWN in just one week. Wazzup? Is this something long
BF> overdue perhaps?
Yes, there is that. I have no pocedure for checking if the nodes in the list
are still up. Sometimes I manually take spot checks, but I had not done that in
quite some time. So yes, there was overdue maintenance.
Yesterday evening I had some time and checked them all. I never expected that
many. :(
I had a closer look and could reduce the 6DWN's to 9. Still a lot though. Two
could be eliminated due to an errror in binkp.net. For 5020/9696 and 463/877
the AAAA record appears in the host name as in the nodelist, but not in
binkp.net. Very odd.
The problem with Jeff Smith's nodes has been solved.
That still leaves 4 that have stopped advertising an AAAA record, 4 that give a
time out on IPv6 and 1 that gives a socket error on unreachable host.
Let's hope the problems can be fixed.
Cheers, Michiel
--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: he.net certified sage (2:280/5555)
|