On 8/04/2011 10:11 p.m., Tony Finch wrote: > No, only DNS requests that are handled by the server itself are cached. > There is no sniffing going on. > > Tony.
Thank you for the clarification. If I add "nameserver 127.0.0.1" to the VM (and comment out the existing name servers) and attempt to resolve a DNS entry, the I see output similar to the following: 08-Apr-2011 22:51:50.116 network unreachable resolving 'www.redhat.com/A/IN': 2001:500:2f::f#53 08-Apr-2011 22:51:54.023 network unreachable resolving 'www.redhat.com/A/IN': 2001:503:c27::2:30#53 08-Apr-2011 22:51:54.024 network unreachable resolving './NS/IN': 2001:503:c27::2:30#53 I understand that this is because there is no upstream DNS for BIND as configured in my named.conf. However, if I try to add a forward forwarders { 192.168.239.2; }; (where the host 192.168.239.2 is "upstream" DNS in my case), then DNS queries are resolved by the client but do not appear to be cached, i.e.: # rndc dumpdb # What am I missing ? Is it not possible to use a "forwarders" directive in combination with a name caching server ? Thanks, Patrick _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users