Subj : WSANO_DATA (11004)
To   : Wilfred van Velzen
From : Michiel van der Vlist
Date : Thu Apr 06 2017 00:19:12

Hello Wilfred,

On Wednesday April 05 2017 21:33, you wrote to me:

 MvdV>> So it is not IPv6 related, but related to IPs that do not
 MvdV>> backresolve.

 WV> It seems so. The windows binkd version should be improved to handle
 WV> this situation more gracefully...

Yes, the error message is not all thet informative as it is.

OTOH, I do not find the backresolve function all that usefull in itself. There is a reason I had it disabled. It slows things down and especially in the case of IPv6 it does not provide very usefull information. Sometimes it resolves, ever so often it does not. 
All Ziggo native IPv6 numbers resolve to ipv6.dynamic.ziggo.nl.

Your IPv6 number does not resolve en neither does that of Kees. Joe's IPv6 address resolves.

- 05 Apr 19:54:28 [436] incoming from 2607:f2c0:a000:54:6ef0:49ff:fedb:3822 (449498)
+ 05 Apr 19:54:28 [1604] incoming session with node-4stumtkuebu8foqrgv6.ipv6.
                         t4stumtkuebu8foqrgv6.ipv6.teksavvy.com
                         [2607:f2c0:a000:54:6ef0:49ff:fedb:3822]
- 05 Apr 19:54:28 [1604] SYS The Lion's Den
- 05 Apr 19:54:28 [1604] ZYZ Joe Delahaye
- 05 Apr 19:54:28 [1604] LOC Trenton, Ont. Cdn
- 05 Apr 19:54:28 [1604] NDL 115200,TCP,BINKP



Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20161221
 * Origin: he.net certified sage (2:280/5555)

.