On Wed, Mar 03, 1999 at 05:18:21PM -0300, Adalto Silva Correia Filho wrote:
>
> Hi D.,
>
> > First thing you can do is try increasing the size of your ipcache and
> > fqdn cache in the config. Double 'em. Triple 'em. Add a zero. That'll
> > hold you some until you can address the _real_ problem, which is that
> > name lookups on the DNS machine aren't completing in a timely fashion.
> >
> Ok. I'll do it and see what happens next.
>
> > Off the top of my pointy little head, I see a couple possibilities:
> >
> > 1) Your DNS box is too busy. Point to a less heavily loaded DNS server.
>
> That could be a point! Is there any tool to measure the overload
> upon a DNS Server? (Iagh! That one was way out off topic, wasn't it? :)
I think it's relevant to people on this list.
For testing your DNS, do some lookups (each one twice) with dig. If your
/etc/resolv.conf
points to a very close DNS, dig should report a very fast 'Total query time' for
anything
you're requesting for the _second_ time. If the first lookup for a certain host is
_very_
slow, you might have a network problem. If the second lookup is just as slow, then
your DNS server is majorly overloaded.
Greetz, Peter.
--
.| Peter van Dijk | <mo|VERWEG> stoned worden of coden
.| [EMAIL PROTECTED] | <mo|VERWEG> dat is de levensvraag
| <mo|VERWEG> coden of stoned worden
| <mo|VERWEG> stonend worden En coden
| <mo|VERWEG> hmm
| <mo|VERWEG> dan maar stoned worden en slashdot lezen:)
