Hello Tony!

03 Jul 19 14:40, you wrote to All:

 TL> This only happens with one particular uplink, as far as I can tell, and
 TL> because the error appears to refer to DNS lookups, I've tried things like
 TL> hardcoding entries in my hosts file, and even using the raw IP:PORT in
 TL> binkd.conf. Anyway, this is the error I get:


 TL>   03 Jul 14:27:02 [16069] started client #1, id=16166
 TL>   03 Jul 14:27:02 [16166] created /sbbs/binkd/fsxnet.015/00010064.csy
 TL> + 03 Jul 14:27:02 [16166] call to 21:1/100@fsxnet
 TL> + 03 Jul 14:27:02 [16166] getaddrinfo failed: Servname not supported for
 TL> ai_socktype (-8)

 I tried 3:633/410 and 3:633/280 and got IPv6 connections on both.
 You are however calling 21:1/100@fsxnet. I have no way to check what
 is in your binkd.conf for that node,

 I expect Servname to be the service port (eg 24554) and the socket type
 either for ipv4 or ipv6.

 I tried 3:633/280 with an arbitrary port number, that resulted in
 connection refused.

 TL> + 03 Jul 14:27:02 [16166] holding 21:1/100@fsxnet (2019/07/03
 TL> 14:37:02)
 TL>   03 Jul 14:27:02 [16166] unlinked `/sbbs/binkd/fsxnet.015/00010064.csy'
 TL>   03 Jul 14:27:02 [16166] bsy_remove_all: done
 TL>   03 Jul 14:27:02 [16069] rc(16166)=0

 TL> I'm not sure what "Servname not supported for..." means.  Google was very
 TL> vague on this, and why it's only appeared in the last month or so is
 TL> baffling me. Looking up the offending hostname in DNS manually using
 TL> nslookup and friends works fine.

 TL> This is the version I'm running.

 TL>   01 Jan 17:30:14 [20916] BEGIN, binkd/1.0.4/Linux -P 3:633/280 binkd.conf

 O.K. that is your local system, not the server for 3:633/410
 It could use an upgrade on the version of Binkd.

 Why does it say: "call to 21:1/100@fsxnet", when you are polling 3:633/410

 Sorry, just more questions and no answers to your problem.

 TL> --- SBBSecho 3.03-Linux
 TL> (3:633/410)

Kees

--- GoldED+/LNX 1.1.5--b20180707