= Сообщение: 3506 из 12523 ====================================== ENET.SYSOP = От : Kees van Eeten 2:280/5003.4 14 Feb 16 23:13:40 Кому : Benny Pedersen 14 Feb 16 23:13:40 Тема : INA:fx.nx.zx.fidonet.net in the current nodelist FGHI : area://ENET.SYSOP?msgid=2:280/5003.4+56c1044c На : area://ENET.SYSOP?msgid=2:230/0+56c0eec6 = Кодировка сообщения определена как: LATIN-1 ================================ ============================================================================== Hello Benny!
14 Feb 16 21:12, you wrote to me:
KvE>> The following lines can be found in the current nodelist: KvE>> ,47,4F_Group,Kharkov,Stas_Filshtinskiy,00-00-000000,300,MO,CM,IBN,INA KvE>> :f47.n461. z2.fidonet.net
BP> brain dead maintainers add fidonet into the nodelist ina deserves to get BP> no call, the ina is hostname, not a fidonet hostname, doh
The node probably does not even notice that it is wrong in the nodelist. The current situation may work perfectly for him.
Let me explain: The node 2:461/47 uses binkp.net as its dynamic address DNS service just like you do with noip.me. You get themultipoint.noip.me as hostname Stats gets f47.n461.z2.binkp.net as hostname.
When a new nodelist arrives it's contents is converted to DNS. For you a line is added, probably
f0.n230.z2 IN CNAME themultixpoint.noip.me
The INA:f47.n461.z1.fidonet.net is ignored, because there is already a:
f47.n461.z2 IN A 220.239.203.9
Stas friends all rely in the DNS nodelist as they are proud, that it is an initiative from a sysop in their country and they do not bother about the weekly nodelist, their configs end with: defnode -nd *
For all their contacts Binkd does a DNS query of the form fx.nx.zx.binkp.net
For 2:230/0 the answer is themultxipoint.noip.me and the resolver has to do a second query for themultixpoint.noip.me the get 87.58.2.106 or whatever ip address you have at that moment.
For 2:462/47 the answer wil be 220.239.203.9
All as expected.
BP> 0*0=0 BP> 1*0=0 BP> 1*1=1
BP> fidonet.net > fidonet.net = not found as a result since it point to it BP> self
Let's replace the fidonet.net by binkp.net first.
I have seen that way of reasoning many times, but all forget that binkp.net is also a service to be your DNS hoster.
There is no circular binkp.net > binkp.net There is a binkp.net > ip address
BP> heads up to nodes that send new nodelist entry
That is alway good.
Kees
--- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
