Mass update of TTL and serial

Kevin Darcy kcd at chrysler.com
Mon May 4 20:54:48 UTC 2009


Next stage of evolution = Dynamic Update. Never have to futz with 
bumping serial numbers ever again.

- Kevin

Bradley Giesbrecht wrote:
> You may find named-compilezone useful to get your zone files in a 
> consistent format before performing your mass update.
>
> //Brad
>
> On May 2, 2009, at 3:39 PM, Scott Haneda wrote:
>
>> I client of mine has thousands of DNS zones that will need a ttl 
>> chance and a serial bump. I want to set a relevant ttl to 300 for a 
>> few days.
>>
>> After that, an IP address change will be made, and I would like to 
>> change the TTL back to something sane. The general format of the zone 
>> looks something like below.
>>
>> Any suggestions on the best way to go trough these? Some will have 
>> variations on them, like some have mx records, most do not:
>>
>> $TTL 1D
>> @ IN SOA ns2.example.com. dns.example.com. (
>> 2009041300 ; serial, todays date + todays serial #
>> 8H ; refresh
>> 2H ; retry
>> 4W ; expire
>> 1H ) ; minimum
>> @ IN NS ns2.example.com. ;Primary Nameserver
>> @ IN NS ns1.example.com. ;Secondary Nameserver
>>
>> ; http website base
>> @ IN A 000.122.226.210
>> www IN A 000.122.226.210
>>
>> Would the "refresh" be the best value to target in this case?
>>
>> -- 
>> Scott * If you contact me off list replace talklists@ with scott@ *
>>
>> _______________________________________________
>> bind-users mailing list
>> bind-users at lists.isc.org
>> https://lists.isc.org/mailman/listinfo/bind-users
>
> _______________________________________________
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
>




More information about the bind-users mailing list