Subj : binkd error
To   : All
From : Tony Langdon
Date : Wed Jul 03 2019 14:40:22

I've been running binkd fairly successfully for 2.5 years on this system, and
for the most part, it's been flawless.  However, on polling one particular
uplink, I've started getting a strange error, which is not giving me a lot of
clues.

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


  03 Jul 14:27:02 [16069] started client #1, id=16166
  03 Jul 14:27:02 [16166] created /sbbs/binkd/fsxnet.015/00010064.csy
+ 03 Jul 14:27:02 [16166] call to 21:1/100@fsxnet
+ 03 Jul 14:27:02 [16166] getaddrinfo failed: Servname not supported for
ai_socktype (-8)
+ 03 Jul 14:27:02 [16166] holding 21:1/100@fsxnet (2019/07/03 14:37:02)
  03 Jul 14:27:02 [16166] unlinked `/sbbs/binkd/fsxnet.015/00010064.csy'
  03 Jul 14:27:02 [16166] bsy_remove_all: done
  03 Jul 14:27:02 [16069] rc(16166)=0

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

This is the version I'm running.

  01 Jan 17:30:14 [20916] BEGIN, binkd/1.0.4/Linux -P 3:633/280 binkd.conf
--- SBBSecho 3.03-Linux
 * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (3:633/410)

.