----------------------------------------------------------------------------------
@REPLY: 2:5001/100@fidonet 6a935d35
@MSGID: 2:5075/35@fidonet 6a93609c
@CHRS: CP850 2
@TZUTC: 0300
@TID: hpt/nbsd 1.9 2024-03-02
Hello Dmitry!
Saturday August 29 2026 22:29, you wrote to me:
ES>> It wasn`t my idea.
DP> So you are against that and now you see the problems with that?
No, I`m not against.
DP> What for? Fixing DNS name is much faster than fixing entry in
DP> nodelist. Do you know how many nodes actually use the current
DP> nodelist?
Not always. As we can see, there are cases where access to DNS name management
is lost, or the DNS domain expires.
To ensure data is up to date, you need to use the up to date DDN, as it contains
all the current information from the latest nodelist.
And anyone can set up a DDN like this on their own.
What`s more, it doesn`t matter at all whether the nodelist uses IP addresses or
DNS names: both must be up to date.
However, in the event of problems with the DNS name, this method allows the node
to remain accessible from the outside if it uses a static IP address.
DP> Did you check https://nodelist.fidonet.cc/ ?
I didn`t.
Eugene
... It`s full of stars!
--- GoldED+/BSD 1.1.5-b20260828 (NetBSD 11.0 Intel Core Haswell)
* Origin: FireFox Station (2:5075/35)
SEEN-BY: 221/0 280/464 5003 5555 301/1 310/31 335/364 341/66 5001/100 5015/46
SEEN-BY: 5019/40 5020/715 1042 1146 4441 5030/1081 5051/44 5053/58 5075/35
@PATH: 5075/35 280/5555 5053/58 5020/715