Maintained by: NLnet Labs

[Unbound-users] unbound does not use "outgoing-interface" for IPv6 TCP requests

Hauke Lampe
Sun Oct 3 14:36:24 CEST 2010


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Hi.

My unbound.conf contains multiple outgoing interfaces:

> outgoing-interface: 85.10.240.249
> outgoing-interface: 85.10.240.250
> outgoing-interface: 2a01:4f8:130:6321::2:0
> outgoing-interface: 2a01:4f8:130:6321::2:1

Unbound uses the configured v4 addresses for both UDP and TCP requests
and v6 addresses for UDP. IPv6 TCP queries are sent with the host's
default address, though:

> 2001:470:1f0b:fde::2.43958 > 2001:500:49::1.53: SWE, [...]
> 2001:470:1f0b:fde::2.43958 > 2001:500:49::1.53: P, [...] DNSKEY? InfO. ar: . OPT UDPsize=65432 OK (33)

Does anyone else see that behaviour?

I looked at outside_network_create() and outnet_tcp_take_into_use() in
services/outside_network.c but didn't see anything obvious.

Unbound version is 1.4.7/svn rev. 2274


Hauke.


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)

iEUEARECAAYFAkyoeMIACgkQKIgAG9lfHFPM0gCgmwH105Mcunf7EL+goY0vqtsB
JFwAl1iM9XLFWRUvSW9R2uHA9JbdsrA=
=J2yH
-----END PGP SIGNATURE-----