TTL Issues
Jim Reid
jim at rfc1035.com
Fri Apr 6 08:57:05 UTC 2001
>>>>> "Ryan" == Ryan Crouch <ryan at meridiantech.com.au> writes:
Ryan> I recently installed 8.2.3-REL. Deleted all our zone files
Ryan> for the secondary DNS server. When the zone's are
Ryan> transferred over, the TTL value now exists on every line,
Ryan> much like the Bind4 zone files. The primary nameserver has
Ryan> the BIND 8 compatible zonefiles, with the $TTL value set at
Ryan> the top, outside of the SOA. The secondary DNS files dont
Ryan> have the $TTL at the top, after the zone transfer has
Ryan> occurred.
A slave server writes a copy of the zone to a file, not a copy if the
zone file that the master file has. That copy has an identical set of
data for the zone as the master server has. It doesn't have to be
written in exactly the same way. For instance, all the resource
records could have explicit TTLs instead of a $TTL directive at the
top of the file. Or maybe the records in the slave zone file inherit
an explicit TTL from the first record in the file.
More information about the bind-users
mailing list