Cisco Distributed Director

[Dan Considine]

Our primary root server does not have recursion disabled.  Clients point to
our
primary and secondary DNS servers,  in order to resolve a "DD" domain entry
the primary or secondary goes to the DD, get's the ip, caches it, then returns
an
A record to the client.  The SOA record, by default, on the DD states a zero
second TTL,  but it takes the primary and secondary 1 second to do this.   If
there are multiple requests for the DD record within 1 second (which holds
true in our case) the same ip is given out to all clients.  This brakes the
load balancing expected from  the DD.  My question is this,  how can I have
the clients go to the DD themselves for the A record without bypassing the
primary and secondary DNS servers?

Thanks in advance..


Cricket Liu wrote:

> > In article <39492DB4.4BBCF4D at exchange.ml.com>,
> > Dan Considine <dconsidine at exchange.ml.com> wrote:
> > >Is there a way to setup non-recursion on an NS record in Bind 4.9.7?  I
> > >need to have client queries sent to my Distributed Director for
> > >resolution,  TTL on the Director is set to "0",  root server takes 1
> > >second to cache this record which
> > >defeats the purpose of the "0" TTL.    Any ideas?
> >
> > I'm not sure what you're talking about.  Our DD's only return SOA and A
> > records for the names that we delegate to them, they don't return the NS
> > records at all.  So the TTL that's used is from the delegation record in
> > the parent domain.
>
> And what the heck does "root server takes 1 second to
> cache this record..." mean?  The root name servers have
> recursion disabled, so they don't cache.
>
> cricket
>
> Acme Byte & Wire
> cricket at acmebw.com
> www.acmebw.com
>
> Attend the next Internet Software Consortium/Acme Byte & Wire
> DNS and BIND class!  See www.acmebw.com/training.htm for
> the schedule and to register for upcoming classes.