[Unbound-users] Interesting issue

[W.C.A. Wijngaards]

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

Hi Steve,

The caches are not accepting queries from the new point?
Possibly resolv.conf on the server does not point to 127.0.0.1 but
elsewhere (which does work somehow), which explains why it can resolve
but the others cannot.

With tcpdump or wireshark see if queries get replies from those two
caches, and that those replies contain valid data.

Or use dig for troubleshooting queries across your network.

Best regards,
   Wouter

On 10/28/2009 04:15 PM, Steve Cole wrote:
> This may be something that is obvious or that is behaviour that is expected by 
> Unbound.  Here's my issue.
> 
> I have two large-ish (rrset_cache set to 300MB) caches at the front of my 
> network nearest the egress to the Internet.  On a WAN at a stub office (with 
> WiMax towers connected) is another network, which I set up unbound on as well 
> and pointed at the caches at the front of the network using:
> 
> forward-zone:
>        name: "."
>        forward-addr: 199.246.2.4
>        forward-addr: 199.246.2.115
> 
> The machine itself can resolve addresses using this configuration, but none of 
> the systems on the network can resolve.  Taking the forward-zone out, they 
> resolve perfectly.
> _______________________________________________
> Unbound-users mailing list
> Unbound-users at unbound.net
> http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iEYEARECAAYFAksKZjgACgkQkDLqNwOhpPgCFACeJm/8kOIeSC6qkHjukUPlZEKm
YO8AoJME+OrYBFgz612kt9Ko0BKKS+G6
=ms7g
-----END PGP SIGNATURE-----