[prev in list] [next in list] [prev in thread] [next in thread]
List: bind-users
Subject: Re: low TTL on cache NS
From: dave () umiacs ! umd ! edu
Date: 2005-08-30 13:59:14
Message-ID: 43146631.64585546 () umiacs ! umd ! edu
[Download RAW message or body]
Barry Margolin wrote:
> In article <devqqa$2rcs$1@sf1.isc.org>,
> dave stern <dave@umiacs.umd.edu> wrote:
>
> > I have several mailservers running cache-only nameservice to reduce
> > their
> > external queries. On occasion, we move hosts from one net to another but
> > the
> > Cache-only NS doesn't pick up the IP change we make on the master NS
> > despite the mailserver being listed in the named.conf on the master
> > under
> > also-notify.
> >
> > Is there a way to reduce the TTL on cache-only NS to something really
> > small?
>
> I think there's a max-ttl option that can be used in named.conf.
>
> But realize that this only affects your nameservers and their clients.
> All the other nameservers in the world will go by the TTLs on the
> records in the authoritative server. If you don't want changes to
> propagate quickly to all nameservers, give them short TTLs to begin with.
>
> --
> Barry Margolin, barmar@alum.mit.edu
> Arlington, MA
> *** PLEASE post questions in newsgroups, not directly to me ***
Turns out that
max-cache-ttl
appears to have the desired affect
Thanks
--
=-=-=-=-=-=-=-=-=-=- generated by /dev/dave -=-=-=-=-=-=-=-=-=-=-=-=
David Stern University of Maryland
Institute for Advanced Computer Studies
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic