06 Dec 18 00:38, Michiel van der Vlist wrote to Carol Shenkenberger:

 MV>>> ,100,Shenks_Express,Virginia_Beach_VA,Carol_Shenkenberger,-Unpubl
 MV>>> ished-, 300,XX,CM,INA:shenks.synchro.net,IBN:shenks.dyndns.org

                                [ ... ]

 MvdV> So, a properly configured binkp mailer will see that the IBN flag 
 MvdV> carries a server address. It will use that and nothing alse to 
 MvdV> connect. A binkp mailer will NOT look at the INA flag since that is 
 MvdV> to be used for any other protocol who's flag has no server address 
 MvdV> of its own. But there are no other IP protocol flags. So no mailer 
 MvdV> will ever use the server address from the INA flag. The INA flag is 
 MvdV> dead wood. It is "unreachable code".

I beg to differ.  I know I don't have to explain to you that BinkD (the
de-facto standard) does NOT use the raw nodelist to get the IP address.  It
CAN, if properly configured, use Binkd.Txt, an extraction of BinkP nodes from
the NodeList.

Jerry Schwartz's Perl script is probably the most popular extraction tool used
to generate this file.  Up until July of this year a file created by this
script was hatched into the I-BinkD file echo.

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

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

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

The data attached to the INA flag in this example is NOT dead wood.  It is
usable if you use the software I have mentioned above.

--- Msged/NT 6.0.1