Добро пожаловать, Гость. Пожалуйста авторизуйтесь здесь.
FGHIGate на GaNJa NeTWoRK ST@Ti0N - Просмотр сообщения в эхоконференции IPV6
Введите FGHI ссылку:


Присутствуют сообщения из эхоконференции IPV6 с датами от 31 Jul 11 14:37:00 до 01 Apr 24 00:03:00, всего сообщений: 7402
Ответить на сообщение К списку сообщений Предыдущее сообщение Следующее сообщение
= Сообщение: 5582 из 7402 ============================================= IPV6 =
От   : Ivan Kovalenko                   2:5057/53          09 Jul 18 14:28:16
Кому : mark lewis                                          09 Jul 18 14:28:16
Тема : 2:5057/53
FGHI : area://IPV6?msgid=2:5057/53+5b433af8
На   : area://IPV6?msgid=1:3634/12.73+5b3ffc36
= Кодировка сообщения определена как: CP866 ==================================
Ответ: area://IPV6?msgid=1:3634/12.73+5b43b89a
==============================================================================
Hello, mark.

06 Jul 18 19:25, you wrote to Benny Pedersen:

VS>>> that I can use the INA:fido.sibptus.ru flag all right, but
VS>>> cannot use the INA:node49.net5005.sibptus.ru flag? Why?

BP>> it does not work since binkd only handle single root-domain in
BP>> binkd.cfg

ml> binkd.conf does allow for different lookup domains... simply specify
ml> them on the domain line...

ml> the real question is if the FTN othernets provide DNS zone lookups for
ml> their networks that binkp.net provides for fidonet...

BP>> try in cfg:
BP>> root-domain sibptus.ru

ml> comment that out and never use it again...

Does this mean that the requirement of FTS-5004 to exclude
nodes which have INA flag referring to a fN.nN.zN.example.org
domain is a bit phony? To me, it sounds so, as the legacy software
doesn't (and it obviously can't) rely on it, while it solely
serves to help IP nodes reaching each other.

Let me allow to quote its few statements:

(a) "The fidonet.net domain however was lost for the Fidonet
community in 2011 when the keeper allowed it to expire."

(b) "...it is strongly recommended that implementations that make use
of a DDN service allow the user to easily configure the root domain
and to configure overrides for often used stationary links..."

Keeping in mind quoted above, this one

"If the INA flag (or any of the protocol flags) of any node carries
host name built from the FTN address using DDN or any other method,
that node MUST be skipped and MUST NOT appear in resulting NS zone.
In general, such names SHOULD NOT appear in the nodelist."

doesn't really look good, since as stated in (a), nobody in Fidonet
is able to get the proper domain name anymore, and (b) we're now
on our own. Hence that, it's merely a question of proper implementation
and its configuration.

So, for the resume (though I guess this is the question for Alexey
Vissarionov) -- what's the big difference, on my own example,
between f53.n5057.z2.binkp.net and fido.roswell.systems ?

Best regards, Ivan.

--- GoldED+/LNX 1.1.5-b20130515
* Origin: Area 51 (2:5057/53)

К главной странице гейта
Powered by NoSFeRaTU`s FGHIGate
Открытие страницы: 0.034238 секунды