Multiple $TTL values

[Woodworth, John R]

Hello,

We've recently noticed multiple $TTL values in transferred zonefiles which do not exist in the original zonefiles.  They appear to be aggregates of TTLs set for individual records and I am definitely a fan of the organized look and feel.

However, I am curious about how they should be interpreted where $ORIGIN is concerned.  I just re-read rfc2308 and it states quite simply:
"   All resource records appearing after the directive, and which do not
    explicitly include a TTL value, have their TTL set to the TTL given
    in the $TTL directive. "

My confusion is $ORIGIN basically defines the default origin while reading in the file and creates a mini-universe for interpreting records until redefined.  Would a $TTL after a $ORIGIN be encapsulated by and restricted to records within that $ORIGIN block?

My gut tells me no, and to follow the RFC literally (or loosely stated "from this point down") but looking at the file it seems as if the $TTL is intended to be for the records within the $ORIGIN only (i.e. it is not reset to global value at the end).

I need to investigate this more on my own but I thought it might prove useful to ask the group as part of my research.


Thanks in advance,
John

-- THESE ARE THE DROIDS TO WHOM I REFER:
This communication is the property of CenturyLink and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20160922/000363a6/attachment.html>