On 2018 Dec 06 21:01:08, you wrote to Fred Riccio:

 FR>> Carol's entry in that extraction of NodeList.224 is...

 FR>>    Node 1:275/100@fidonet  shenks.dyndns.org;shenks.synchro.net    -

 FR>> which is causes BinkD to try the dyndns.org host first, if it doesn't
 FR>> resolve it tries the synchro.net address.

 MV> Then obviously the combination of Jerry's script and binkd does not
 MV> qualify as a properly configured FTSC complient software.

it is absolutely properly configured... it works exactly as binkd intends it to
work... the result is also exactly as intended, too... that result is that
xxcarol's system is available via another domain name if one of them fails for
some reason (eg: dyns updater doesn't update the domain entry)... if both/all
domains are unresponsive, then sure, there may be a problem on that system...
if only one dyns updater fails, it is not as big a problem because the other
domain should still be working... radius/argus/taurus all work the same way
except they also have finer capabilities in that they handle more protocols
than just IBN so their node list format is more detailed and their convertor(s)
may not use the same data in the same way... they should but those mailer devs
are quite quiet in recent years and i'm not sure who is maintaining their
convertors... scott little would know more on that since he generates the
distributed ARGUS.TXT file...

)\/(ark

Always Mount a Scratch Monkey
Do you manage your own servers? If you are not running an IDS/IPS yer doin' it
wrong...
... smoke gets in your eyes....
---