Re: Changing $TTL for many zones

In article <cemtb9$1nvg$1@sf1.isc.org>,
Kevin Darcy <kcd@daimlerchrysler.com> wrote:

> Barry Margolin wrote:
>
> >In article <cemkbf$14n1$1@sf1.isc.org>,
> > Kevin Darcy <kcd@daimlerchrysler.com> wrote:
> >
> >
> >
> >>Exactly. I would go further and suggest that, since the SOA needs to be
> >>changed anyway, just give an explicit TTL to the SOA RR, and thus
> >>dispense with the $TTL directive completely (my assumption here is that
> >>the SOA RR is the first RR in the zone file).
> >>
> >>
> >
> >What is this supposed to accomplish? Putting an explicit TTL on the SOA
> >record doesn't create a default for the rest of the file; that's what
> >$TTL is for.
> >
> Giving the first RR in the zone file an explicit TTL is functionally
> equivalent to establishing a default TTL value, if none of the other
> records have an explicit TTL.

I've never heard of that. TTL is not automatically inherited from one
record to the next. Any records that don't have an explicit TTL get the
default that's specified in $TTL.

If you don't have $TTL specified, the default will come from the MinTTL
field of the SOA record, for backward compatibility with BIND versions
that predated $TTL.

--
Barry Margolin, barmar@alum.mit.edu
Arlington, MA
*** PLEASE post questions in newsgroups, not directly to me ***