[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: Jeff Nelson <jnelson_(_at_)_jgndesigns_(_dot_)_com>
- Date: Tue, 2 Nov 2004 23:50:29 -0500
- Mail-followup-to: misc_(_at_)_openbsd_(_dot_)_org
On Tue, Nov 02, 2004 at 04:39:03PM +0100, Otto Moerbeek wrote:
> On Mon, 1 Nov 2004, 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
> > suggestions?
> I'm seeing the same behaviour here on a 3.5 named: it's waits a couple
> of seconds before querying an external DNS server, if it has not cached
> the result.
> In my case, restarting named caused the problem to disappear.
> I'm cc'ing the maintainer of named to see if he has a clue.
Same behavior on my 3.5 named. Started about 60 days ago. Restarting
named was of no help for me.
After a fresh (CD) install of 3.6 the problem has disappeared.
Visit your host, monkey.org