= Сообщение: 3490 из 12523 ====================================== ENET.SYSOP = От : Kees van Eeten 2:280/5003.4 13 Feb 16 17:23:10 Кому : BjЎrn Felten 13 Feb 16 17:23:10 Тема : INA:fx.nx.zx.fidonet.net in the current nodelist FGHI : area://ENET.SYSOP?msgid=2:280/5003.4+56bf617e На : area://ENET.SYSOP?msgid=2:203/2+56bf3fb4 = Кодировка сообщения определена как: LATIN-1 ================================ Ответ: area://ENET.SYSOP?msgid=2:280/5555+56bf6b72 ============================================================================== Hello BjЎrn!
13 Feb 16 15:37, you wrote to me:
BF> You know that I knew that, yes? 8-)
;)
BF> My point was: why even add any fx.nx.zx URL to the nodelist? Just BF> go BF> with the present flow and accept the present best known service.
You can only do that if you are sure, that listing only the BNL flag means that you have to look for fx.nx.zx.binkp.net and you rely fully on the binkp.net DNS services.
Some 24 systems do think that is sufficient. They use binkp.net as their dynamic host DNS provider. Another 44 are also listed in the nodelist, and 11 are listed, but no longer registered.
BF> After all, some of those nodes that you list over and over again BF> are BF> obviously dead wood. They have Down listed nodes for years, they still BF> have URLs that's been defunct for many years.
Yes, but it takes some persuasion to have them removed, I am just another sysop.
BF> I don't know what that Swedish nodelist error flag program that BF> Ward is BF> using can do about it, but I for one would advocate removing every BF> fx.nx.zx URL from the nodelist.
I am not aware that ERRFLGS can do that, but it could be added. It is written in Pascal, not my favoured language. Besides you would have to convince Ward to use it.
But you can only remove those entries if you agree that binkp.net is the default. However, there are also entries of the form fx.nx.zx.otherdomain.
I could use f5003.n280.z2.ddutch.nl and f5006.n280.z2.ddutch.nl
I will have to check, maybe that is already a valid address, and if not, I could put it in my domain file right away.
Why should those addresses be removed and your eljaco.se persist.?
We could go to the extreem: force every node to register with binkp.net and remove all hostnames from the nodelist. ;(
I did check my domain file, but there is no f5003.n280.z2.ddutch.nl nor a 5006......
I do derive a domainfile from the daily nodelist, so if I merge that file with my current domain file there would be a fx.nx.zx.ddutch.nl service similar to binkp.net.
Kees
--- GoldED+/LNX 1.1.5 * Origin: As for me, all I know is that, I know nothing. (2:280/5003.4)
