[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Delay in named response
- To: misc_(_at_)_openbsd_(_dot_)_org
- Subject: Re: Delay in named response
- From: Pete Wieckowski <pwieckowski_(_at_)_gmail_(_dot_)_com>
- Date: Tue, 2 Nov 2004 10:14:12 -0800
I'm seeing this as well on 6 of my nameservers here running both 3.5 and 3.4.
I'm going to upgrade a couple of them to 3.6 to see if it resolves the issue.
On Monday 01 November 2004 18:45, Todd Pytel wrote:
> Hi misc@,
> 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...
> Nothing in my named configuration has changed in over a month, so I
> can't see what named.conf would have to do with it. Cached queries and
> other connections with the server (pings, web requests, etc.) have no
> problems at all, so it doesn't look to me like a hardware problem.
> There's nothing unusual in any logs whatsoever.
> I'd be happy to provide any further information that would be helpful in
> diagnosing this, but I don't even know where to start looking. Any
> Todd Pytel
Visit your host, monkey.org