AV> That means, my node will try to resolve fido.vlist.eu first (as this AV> hostname appears in the nodelist), but if that fails, it will try both AV> IPv6 and IPv4 addresses (once known to be static).
I appreciate the way you solve this and it shows your profession experience.
My approach is slightly different and a bit more relaxed. In my main binkd.links there is a line:
node 2:280/5555 - [password]
In a what some would call binkd.txt, in my case locally derived from the daily nodelist, there is a line:
node 2:280/5555 fido.vlist.eu -
fido.vlist.eu resolves to an IPv6 and an IPv4 address, so first a connection is tried over IPv6.
In principle fido.vlist.eu resolves to a dynamic IPv4 address, so putting it in a configuration file, does require maintenance to your binkp.links. In principle you are covered when the IPv4 address changes, as fido.vlist.eu is used first.
But all in all the configuration options are very flexible and can adapt to almost anybodies taste.
Kees
--- FPD v2.9.040207 GoldED+/LNX 1.1.5--b20130910 * Origin: As for me, all I know is that, I know nothing. (2:280/5006.4)
