Cache strangeness
Mark_Andrews at isc.org
Mark_Andrews at isc.org
Thu Nov 7 00:15:00 UTC 2002
> >
> > >
> > > This is not a function that we wish to support, can this be turned off?
> >
> > Do you really know the impact of turning this off?
> >
> > The root servers are currently spend the vast majority of
> > there time (> 90%) repeatedly answering negative queries
> > that could have been avoided if the clients supported
> > negative caching.
> >
> > Yes, you can tune it but don't turn it off. You are doing
> > a disservice to everyone if you do so.
> >
>
> Ok, I'm starting to see the rational behind this now. I guess the major
> problem in my case was that the domain in question had such a high ttl that
> this problem came up. Normally with 3 hours I doubt that this would be an
> issue, but the question I have now, is why did it appear to cache longer
> than the default?
You said that the master for the reverse died. The slave
continued to hand NXDOMAIN until it was able to update the
zone from the master.
Mark
>
> --
> -----BEGIN PGP SIGNATURE----- Robert Weber
> <!-- |**|begin egp html banner/ UnixOps/ITS
> > Thank you for registering There is no catch. University of Colorado
>
> > this e-mail blah blah confidential and yadda yadda legally privileged
--
Mark Andrews, Internet Software Consortium
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742 INTERNET: Mark.Andrews at isc.org
More information about the bind-users
mailing list