In message <4a53cf4a.8050...@provident-solutions.com>, "Vernon A. Fort" writes:
> Mark Andrews wrote:
> > In message <4a452428.9020...@provident-solutions.com>, "Vernon A. Fort" wri
> tes:
> >
> >> I've run into a problem with named and timeouts primarily with MX
> >> lookups. When a MX query
Mark Andrews wrote:
In message <4a452428.9020...@provident-solutions.com>, "Vernon A. Fort" writes:
I've run into a problem with named and timeouts primarily with MX
lookups. When a MX query fails the first time, i have to restart the
named process before it will return a successful query.
In message <4a452428.9020...@provident-solutions.com>, "Vernon A. Fort" writes:
> I've run into a problem with named and timeouts primarily with MX
> lookups. When a MX query fails the first time, i have to restart the
> named process before it will return a successful query. Again, its
> mai
To:
Sent: Friday, June 26, 2009 1:40 PM
Subject: DNS MX timeouts
I've run into a problem with named and timeouts primarily with MX lookups.
When a MX query fails the first time, i have to restart the named process
before it will return a successful query. Again, its mainly with MX
look
On Fri, Jun 26, 2009 at 02:40:24PM -0500,
Vernon A. Fort wrote
a message of 31 lines which said:
> All versions of bind i have tried (in gentoo portage) have the same
> problem.
Well, my personal dedicated server is a Gentoo using BIND as a
resolver and I can say it works. So, no real ideas,
I've run into a problem with named and timeouts primarily with MX
lookups. When a MX query fails the first time, i have to restart the
named process before it will return a successful query. Again, its
mainly with MX lookups but it also happens with A records as well. The
problem subsides fo
6 matches
Mail list logo
