Zitat von "W.C.A. Wijngaards" <[email protected]>:

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

Hi Andreas,

On 11/02/2010 11:38 AM, [email protected] wrote:
The request is orginating at localhost with "nameserver 127.0.0.1" as
the only content in resolv.conf so routing should not be the problem. If
have disabled "interface-automatic: yes" because the machine is
multihomed and have bound unbound to the needed interfaces "by hand"
with the "interface:" statement. I have also set "do-ip6: no" because
the machine has ipv6 capabilities but no ipv6 connectivity until yet.

Looks like this is reasonable config to me.

So the packetdump was from the eth interface, and did not include lo0
traffic, that is why the reply is not in the packet capture?

Best regards,
   Wouter

The packet capture is from the connection unbound (10.5.0.1) -> upstream bind (10.5.0.3) to see if bind deliver results or not. If have done no localhost capture but i can try later. It is a bit difficult because it's the main resolver for the internal net and people don't like to be without internet access today ;-)

Regards

Andreas


_______________________________________________
Unbound-users mailing list
[email protected]
http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users

Reply via email to