Bind refuse to cache DNS query results

[Kevin Darcy]

The configuration you showed should allow caching of query responses --
in fact, there isn't any way to configure named to *not* cache query
responses. Are you absolutely sure that 127.0.0.1 is the
*first* "nameserver" entry in /etc/resolv.conf? What about the
TTL (time-to-live) values of the records you are querying? If they are
set really small, then maybe the records are timing out the cache
between your queries.

By the way, you can dump your nameserver's cache with "ndc dumpdb" or
sending an INT signal to the "named" process. That should be proof
positive whether the entries are getting into the nameserver's cache or
not.


- Kevin

jajoo_sg at my-deja.com wrote:

> Hi,
>
> I have just installed Bind 9.01 on a Solaris 2.7
> machine. I intend to use it as a query cache to
> reduce the need to always contact the primary DNS
> Server.
>
> However, sniffing the network concludes that all
> local requests still goes to the primary DNS
> Server! (I have modified /etc/resolv.conf to
> point nameserver to 127.0.0.1). It does not seem
> to be able to return unauthoritative responses.
>
> Does anybody know how I can configure Bind to
> cache previous successful and unexpired queries?
>
> Any help is much appreciated.
>