Subj : Weekly nodelist report on noteworthy changes (206)
To   : Nodelist Police Commissioner
From : Deputy Nodelist Police
Date : Fri Jul 24 2020 14:46:21

Hello Nodelist,

On Friday July 24 2020 09:20, you wrote to All:

 NC> New node in net 5030:
 NC> ,137,m0t,Peterhof,Matvey_Antonyuk,-Unpublished-,300,CM,IBN,INA:m0t.s0t
 NC> .ru Connect with binkd/1.0a-559/Win32. And although the sysops
 NC> firstnaam is different from that of the host, it identifies it self
 NC> also with nodenumbers 5030/0 and 5030/731.

Cheap trick to obtain sysop status for other member of the household? Son maybe?

 NC> Host,5053,Saratov_Net,Saratov_Russia,Alexander_Tsaplin,-Unpublished-,3
 NC> 00,CM,IBN ,INA:tavsar.mykeenetic.com Has a new host name. It resolves
 NC> to 2 IPv6 and 1 IPv4 address. On the IPv6 addresses there is no
 NC> response.

Sounds familair. This happens more often these days...

 NC>  That might have to do with the older version of
 NC> Binkd/0.9.10/Win32 that's being used on the node.

Possibly. But as I said, it happens more often these days. I wonder if some people get an IPv6 address without being aware of it and it somehow finds its way to the DNS....

 NC> In the other zones there are 0 changes. Only the sequence number in
 NC> the entry for Zone,1,... has been increased. So I suspect something
 NC> might be wrong, because normally other sequence numbers in the Z1
 NC> segment are updated atleast weekly...

I rest my case.. ;-)


Cheers, Deputy

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: Nodelist Police Station (2:280/5555)

.