TID: FMail-W32 2.2.0.0
RFC-X-No-Archive: Yes
TZUTC: 0100
CHRS: CP850 2
MSGID: 2:280/5555 65a4195f
REPLY: 2:460/5858 65a28e1b
Hello Stas,

On Saturday January 13 2024 16:13, you wrote to me:

 MvdV>> I actually managed to extract some new ones. ;-)

 SM> I'm glad that this helps.

It does indeed help.

 MvdV>>  and apparently you only check if the listed host name
 MvdV>> resolves.

 SM> I'm checking to see how he resolves.

 MvdV>> There are quit a few in the list that only answer on IPv4 or
 MvdV>> not at all.

 SM> If you look at the error text, you will see a large number of nodes
 SM> there whose domain names are not resolved at all. This may be useful
 SM> for a nodelist cop. ;)

Usefull indeed. But I was referring to nodes who's host name resolves to an
IPv6 address but that do not connect via IPv6. E.g. 2:263/5.

 WV>>> 56. 2:31/0      Helmut Renner
 WV>>> fd14:7740:62f:4800:3a10:d5ff:fe93:7e79 57. 2:31/2      Helmut
 WV>>> Renner fd14:7740:62f:4800:3a10:d5ff:fe93:7e79

 MvdV>> A ULA, that should not be in the nodelist. Helmut needs an
 MvdV>> update on IPv6 101. ;-)

 SM> Surprise! ;)

Send him netmail, no response yet.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
 * Origin: he.net certified sage (2:280/5555)
SEEN-BY: 1/19 15/0 16/0 19/10 37 90/1 104/117 105/81 106/201 123/130
SEEN-BY: 128/260 135/225 142/104 153/7715 203/0 218/700 221/0 1 6
SEEN-BY: 221/360 226/30 227/114 229/110 112 113 206 307 317 400 426
SEEN-BY: 229/428 470 550 616 664 700 230/0 240/1120 5832 250/1 266/512
SEEN-BY: 280/464 5003 5006 5555 282/1038 291/111 292/854 301/1 310/31
SEEN-BY: 320/119 219 319 2119 322/757 342/200 396/45 423/81 460/58
SEEN-BY: 633/280 712/848 5019/40 5020/545 1042 5053/58 5075/35
PATH: 280/5555 221/1 320/219 229/426