> This is a common point of confusion. DNS does not transfer > zoneFILES. Zone files are read and converted into the > in-memory tree structure. Zones are sent in wire format > from the in-memory tree. The receiving end populates its > in-memory tree. It can then convert the information to > zone file format, and write it out, but do not expect it > to look anything like the original zone file. It has no > idea what the original file looked like, or what order the > records were in. > > $ORIGIN and $TTL only apply to the zone they are in, so no > need to reset them at the end of the file since they cease > to exist at that point. They apply "from this line down > until changed" and are merely a convenience to shorten > the size of the file. > > -- > Bob Harold > >
Bob, Thanks for your response. Although I was aware the zone data is transferred in wire-format between nameservers I was more concerned with the processing of the file when it is read (i.e. on startup, reconfig, etc.) We are "lucky" enough to be importing more zones into a DB backed provisioning system and as bind is getting more and more strict with each release regarding transfers we have scrapped our older scrubbing logic and started using bind to provide this service and couldn't be happier. Just wanted to confirm this $TTL logic was exactly as I suspected before requiring code changes (non-bind). Thanks again, 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.
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
