Subj : FTS-5004
To   : Oli
From : Pavel Gulchouck
Date : Sat Sep 17 2022 05:03 pm

Hi Oli!

16 Sep 22, Oli ==> Pavel Gulchouck:

[...]
 PG>> Sorry, it's not about using binkp.net by sysop in the mailer for resolve
 PG>> nodes. Sure, nobody can forbid it. It's about using binkp.net in INA flag
 PG>> in the nodelist - Alexey says it's XAB because it violates FTS-5004.

 Ol> Now I get it. I would agree that it is problematic, because the z*.binkp.net namespace also includes records that are generated from
 Ol> the nodelist.

What problem do you see with this?
Obviously if it's address from node.binkp.net that it will work, and if not, that it is unresolvable address.
There will be no CNAME loop in generated binkp.net by nodelist with such INA.

 Ol> Why not use *.dyn.binkp.net and *.node.binkp.net addresses in the nodelist -> problem solved.

Not solved, because using of *.dyn.binkp.net and *.node.binkp.net also violates FTS-5004.
These zones are not generates by nodelist, but they use the same hostname generation nNN.fFF.zZZ.domain which is prohibited in INA flag by the FTS.

              Lucky carrier,
                           Pavel
                           aka  gul@gul.kiev.ua
--- GoldED+/LNX 1.1.5-b20160827
 * Origin: Lucky Carrier BBS (2:463/68)

.