Bugzilla – Bug 362
outgoing-interface and v4 vs. v6 leads to spurious warning messages
Last modified: 2011-02-24 14:26:47 CET
In a configuration where you have to use outgoing-interface: and have both IPv4 and IPv6 addresses (i.e. using two outgoing-interface statements, one for v4, one for v6) and where you have secondaries with both v4 and v6 adresses, a
command will lead to spurious messages warning you about skipped secondaries ("no local address family matches remote"). This happens because nsd-notify is called with a -a argument for each outgoing interface (i.e. once for v4, once for v6) and for each secondary address (v4/v6). Now the combination of v4 -a and v6 target creates this warning, as well as v6 -a and v4 target.
A simple workaround would be to use a hostname as -a argument (which seems to work at the nsd-notify level), but unfortunately nsd.conf syntax does not allow this.
Thank you for the bugreport, this one is fixed too. It checks for v4-v6 differences.
Best regards, Wouter