Good ${greeting_time}, Michiel!

28 Mar 2017 11:06:50, you wrote to me:

 FR>>> This method is not to be used to signal that a system is
 FR>>> IPV4 and IPv6 capable. Additional IPv6 capability should
 FR>>> be advertised by adding an AAAA record to an already
 FR>>> listed host name.
 AV>> Wrong.
 AV>> INA:192.0.2.123,INA:[2001:db8:f1d0::1234],IBN is a legal
 AV>> set of flags.
 MvdV> Maybe, but it is not common practise...

Hmmmm... Well, for now there are no literal IPv6 in the nodelist:
% egrep 'INA:\[' ~/fido/etc/nodelist.ndl | wc -l
0

However, the abovequoted paragraph should look like:

==== yum ====
Multihomed systems or systems that are otherwise reacheable by more than one
address, _may_ carry two or more INA flags. That can be used to provide some
redundance, and the recommended way is to use the INA flags with different
server names, each pointing to all IP addresses, so the nodelist entry with
INA:fido.example.com,INA:fido.example.net flags may point to NS zone records
like:

$ORIGIN         example.com.
fido            IN A            192.0.2.123
                IN A            198.51.100.123
                IN AAAA         2001:db8:f1d0::1234

$ORIGIN         example.net.
fido            IN A            192.0.2.123
                IN A            198.51.100.123
                IN AAAA         2001:db8:f1d0::1234

Also, multiple INA flags _may_ (and generally _should_) be used when the NS
zones aren't fully controlled by sysop - for example, when using Dynamic DNS
services (query your favorite search engine for "free ddns" if you need one).

Although multiple INA flags may be used to list both IPv4 and IPv6 literal
addresses, this is not recommended; use domain name instead.
==== burp ====


--
Alexey V. Vissarionov aka Gremlin from Kremlin
gremlin.ru!gremlin; +vii-cmiii-cmlxxvii-mmxlviii

... god@universe:~ # cvs up && make world
--- /bin/vi