From: Kevin (kkadowgmail.com)
Date: Mon Nov 01 2004 - 21:30:31 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

On Mon, 1 Nov 2004 20:45:22 -0600, Todd Pytel <tppytelsophrosune.org> wrote:
> I'm stumped on this one. My nameserver has been happily running 3.5
> since that was released with no problems. But for the last week, I've
> noticed that name resolution has been brutally slow - anything not
> already in the cache takes at least 4 seconds to get a response, which
> is far longer than it used to take. Running some ethereal captures on
> the server's interface reveals that the actual lookups against the
> outside world happen quickly (less than a second), but that my
> nameserver is waiting for about 4 seconds from the time it receives the
> client request until it queries an external nameserver. Like it can't
> decide whether it has the query cached or not...

If you can ensure that no other clients are making queries while
testing, you could try using 'ktrace' (see 'man ktrace', requires
kernel support, can be attached to a running process) to get a feel
for what the daemon is doing during those 4 seconds.

There are also some verbose debugging options which can be enabled in 'named'.

Kevin

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]