Just to make sure I have TTL's understood.

[Scott Haneda]

Sorry about the top post, it is seems more relevant to do it on this  
case.

The zone was created elsewhere, I sort of inherited it.  I have  
hundreds of them, and have found no simply way to reformat the zone  
files.  They are not terribly bas to start, but they are clearly made  
in a way to be read by a tool, rather than edited by hand.

I take the approach of running this across any zone I edit:
named-checkzone -D -s relative example.com hostsfile

Which outputs a file in the format, very close to what I put in my  
original post.  That is why you are seeing the TTL's cascade down like  
that, and the lack of the use of @.

You mentioned a base TTL, where would I set that, just after the SOA  
line, so set my 3600 to 300, and that makes all of them 300, and since  
it is not permanent, that would be ok even if a little agressive?

Or are you saying to set the record to 300 in each case?  ie:
@	300		MX	10 gonepostal.hostwizard.com.

Thanks.


On Nov 25, 2008, at 10:17 PM, Res wrote:

> On Tue, 25 Nov 2008, Scott Haneda wrote:
>
>> ORIGIN .
> ^^^^^^^^^^  not needed
>
>
>> $TTL 86400      ; 1 day
>> example.com              IN SOA  ns1.hostwizard.com.  
>> scott.hostwizard.com. (
> ^^^^^^^ not needed, replace with @
>
>
>>                              2008112501 ; serial *** I did change  
>> this ***
>>                              14400      ; refresh (4 hours)
>
> This is when the slaves will check the master for update, so its  
> every 4 hours.
>
>
>> $ORIGIN example.com.
>
> ^^^^^^^^^ remove, not needed at all, no need to replace with @  
> either in this position.
>
>> $TTL 300        ; 5 minutes
>
>
> this is overly messy, you are better off just setting your base TTL  
> to 300
> and be done with it until your move then reset it all back to 1d.

--
Scott