Caching only servers

[Kevin Darcy]

"Georgeson, Evan [NCSUS Non J&J]" wrote:

>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
>         I'm suffering some bizarre symptoms on my two cache servers. For
> some reason, they stop servicing internal requests and then restart
> after a few minutes. Could there be a load issue?

Yes :-)

> I'm going to give
> you a list of the named.conf options can I get someone to check them
> for validity and confirm correct or no?? Thank you very much if you
> can help or advise.

Your cleaning-interval is set to 4 minutes. That seems a little rabid. Did
you increase the frequency to try to keep your memory usage down? If you
have sufficient memory, I'd relax the cleaning interval. By touching your
memory pages this frequently, you may be forcing them to be resident more
often and actually *hurting* your memory situation.

> Also, is it logged when nslookup queries return nxdomain or servfail,
> e.g., queries.log??

No, I do not believe this is available in the query log.

NXDOMAIN is a fairly routine reponse code; clients ask for non-existent
names all of the time (especially when they are configured with
searchlists, grrrrr....)

SERVFAIL is not so common, but in general, whatever is causing the
SERVFAIL condition is being logged by your nameserver in some other way.
Unfortunately, there are many different things which can give rise to a
SERVFAIL -- it's kind of a catch-all category.

You can try turning up the logging for various categories and/or turning on
debugging, if you want more information on these conditions, but be aware
that this will drive up your resource consumption, which you may not want
to do at this time.


- Kevin