================================================================
A R T I C L E S
================================================================
Errors in INA: Statements in the ZONE 1 Segment
Addendum
By Janis Kracht, 1:1/0,
janis@filegate.net
Mark Lewis, 1:3634/12, sent additional information regarding
INA: usage. Please see below.
Mark Lewis wrote:
JK> All internet flags using the INA: flag should be located
JK> within the INA: statement.
these are correct forms...
INA:some.site.example.tld
INA:127.0.0.1
INA:[::1/128]
these are incorrect forms...
INA
INA:
INA:1234
INA:some.site.example.tld:1234
INA must have a domain or IP number... the IP may be IPv4 or
IPv6 format... just put square brackets around the IPv6
number... see FRL-1036.001 for more information... anything
other than a domain or IP number is incorrect...
ideally you would put your other Ixx flags _after_ the INA
flag...
INA:some.site.example.tld,ICM,IBN,ITN:2323
INA:some.site.example.tld,ICM,IBN,ITN:2323,IVM:site.
invalid:314141 [wraps]
the second example shows a different domain and port for the IVM
flag as well as just a different port for the ITN flag which
takes its domain from the INA flag...
[Editor's Note: the following is important and should have been
mentioned in my earlier article. Thank you Mark!]
JK> Don't put internet flags like ITN BEFORE the INA: flag if
JK> you are using INA:
well, you /can/ but that means that the domain will be taken
from _one_ of the following...
1. the flag itself
OR
2. the system name field
OR
3. from an INA flag - NOTE-3
OR
4. the result of a f.n.z conversion and DNS lookup
(FTS-5004.001) - NOTE-4
NOTE-3: apparently currently used nodelist parsers don't care
what order the flags are in... while you can have multiple INA
flags, they apply to all Ixx protocol flags...
NOTE-4: the conversion of *fidonet* addresses has to be looked
up on binkp.net instead of the original fidonet dns server...
this because a squatter snarffed it up when it expired some
years back and wants too much $$$ to give it back... so
binkp.net was started and runs the same software as the
original... in binkd, this is a specific setting in your config
file... other mailers may be able to be pointed properly unless
they are hardcoded... other FTNs should have their own DNS
server for their othernet domain to perform this lookup
response... this keeps from hitting binkp.net with lookups for
domains it has no clue about...
)\/(ark
FIDOGAZETTE Vol 11 No 33 Page 3 August 16, 2017
-----------------------------------------------------------------
--- BBBS/Li6 v4.10 Toy-3
* Origin: Prism bbs (1:261/38)