My mailer thinks Peter da Silva said:
>
> > Clicking the 'reload' button or any dns cached location succeeds.
> > Could this be a dns problem, or a proxy problem?
>
> Sounds like a DNS problem tickled by CERN. I have the same problem, and
> the symproms are consistent with gethostbyname(3) or named(8) timing out
> on the first DNS request, but by the time the second request is made the
> response to the first's gotten to named and is satisfied from the cache.
>
> I get the problem on a system with a 14.4k PPP link and a local DNS.
>
I used to get the same problem running a split DNS. By the time the
response arrived the resolver on the firewall had timed out. Because
the response was however cached, the reload worked fine. My internal
named.boot used to look like:
forwarders 203.5.10.10
Now it looks like
forwarders 203.5.10.10 203.5.10.10 203.5.10.10
and I no longer have the problem.
Apologies for interposing if the split DNS is not relevant to your
situation(s).
Colin
References:
|
|
