On Fri, 03 Oct 2014, Markus Reschke wrote to Paul Hayton:
PH> At present my nodelist entry uses IBN:agency.bbs.geek.nz to PH> achieve the same kind of outcome it would seem.
MR> Yes, but the recommended method is: MR> ...,IBN,INA:agency.bbs.geek.nz,...
that's actually backwards and/or wasted... the INA should be listed /before/ the flags that it affects... in the above, the shown IBN flag is associated with the preceeding unknown portion of the entry while INA is for the trailing unshown portion of the entry...
this positional distinction seems to be missed by many and the INA flag is wasted as it doesn't get followed by other flags indicating the capabilities available for the connection it is representing...
if the above example does not contain an IP or FQDN in a recognized position before the IBN, then connecting systems will likely be attempting the f.n.z conversion and lookup to find the proper IP or FQDN to connect to for the IBN connection...
