Strange Zone Errors :(

[Kevin Darcy]

Okay, let me see if I have this straight:

1. nameservers get the "real" NS'es (stargate and yoda in this case)
2. the corresponding A records happen to expire from the cache earlier than the
NS'es themselves
3. these A records wouldn't be obtainable from the parent servers because they,
i.e. the parent servers, would have no way of knowing that they, i.e. the
A records for the "real" NS'es, were necessary glue records; and the delegation
NS'es (dns1 and dns2) from the parents would never replace the "real" NS'es as
long as they are cached because the "real" ones are more credible, right?
4. Therefore deadlock occurs (at least until the NS'es expire from the cache and
the cycle starts all over again).

Did I get it?

I wonder if there's an easier-to-comprehend way of explaining this, so that it can
be promulgated and folks will understand that it's more than just a
"hygenic" issue...


- Kevin
Mark.Andrews at nominum.com wrote:

> >
> > Mark.Andrews at nominum.com wrote:
> >
> > > >
> > > > The NS'es in your zone (yoda, stargate) -- at least tsisom.com which is t
> > he
> > > > only one I looked at -- don't match the delegation NS'es (dns1, dns2), bu
> > t
> > > > I don't think that's the source of your problem, since the IP addresses d
> > o
> > > > match.
> > >
> > >         Actually it is likely to be the cause of the problems.
> > >
> > >         I've explained how this is a problem may times before.
> >
> > Sorry, my memory must be failing me today. Could you briefly explain, once mo
> > re,
> > for the record?
>
>         http://www.isc.org/ml-archives/bind-users/1999/10/msg00735.html
> >
> >
> > - Kevin
> >
> >
> >
> >
> --
> Mark Andrews, Nominum Inc.
> 1 Seymour St., Dundas Valley, NSW 2117, Australia
> PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com