Hello Victor!   
      
   05 Jul 2018 12:08, Victor Sudakov wrote to Benny Pedersen:   
      
    MvdV>>> Let's give him and his NC a chance to correct it...   
      
    BP>> it basicly there own problem, but binkp.net should reject ina with   
    BP>> binkp.net listnings   
      
    VS> Last time I checked, binkp.net did not rely solely on DDN, you could    
    VS> enter any RR for your node manually via a Web page (which I did long    
    VS> ago). So if you have created a RR for your node in binkp.net, there    
    VS> should be no technical problem using a binkp.net-derived name in the    
    VS> nodelist flags.   
      
   i did not know its a webpage aswell, if the web lets users create rr that are   
   not in nodelist, hmm :)   
      
    VS> The requirement in FTS-5004   
      
    VS> If the INA flag (or any of the protocol flags) of any node carries   
    VS> host name built from the FTN address using DDN or any other method,   
    VS> that node MUST be skipped and MUST NOT appear in resulting NS zone.   
    VS> In general, such names SHOULD NOT appear in the nodelist.   
      
   +1   
      
    VS> has always seemed technically unfounded (or at least the unarticulated    
    VS> "any other method" statement) to me. Does it mean that I can use the    
    VS> INA:fido.sibptus.ru flag all right, but cannot use the    
    VS> INA:node49.net5005.sibptus.ru flag? Why?   
      
   it does not work since binkd only handle single root-domain in binkd.cfg   
      
   try in cfg:   
      
   root-domain sibptus.ru   
      
   and check logs, for this to work its important   
      
   node  *    
      
   is used if * is not a star it disables root-domain   
      
      
    Regards Benny   
      
   ... there can only be one way of life, and it works :)   
      
   --- Msged/LNX 6.1.2 (Linux/4.17.3-gentoo (x86_64))   
    * Origin: I will always keep a PC running CPM 3.0 (2:230/0)