zone revision f7cf0e6785e4a7e5574328a7000a9e8926a9bc9c
2fee8782a6fd57d86a67949092ab9197111af390Evan Hunt $Id: zone,v 1.2 1999/02/26 21:32:10 marka Exp $
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt Zones are the unit of delegation in the DNS and may go from holding
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt RR's only at the zone top to holding the complete hierachy (private
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt roots zones). Zones are a container for the RRsets that make up the
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt Zone have certain properties associated with them.
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * master / slave / stub / hint / cache / forward
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * serial number
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * signed / unsigned
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * update periods (refresh / retry) (slave / stub)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * last update time (slave / stub)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * access restrictions
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * transfer restrictions (master / slave)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * update restictions (master / slave)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * expire period (slave / stub)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * children => bottom
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * rrsets / data
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * transfer "in" in progress
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * transfers "out" in progress
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * "current" check in progress
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * our masters
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * primary master name (required to auto generate our masters)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * master file name
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * database name
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * transaction logs
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * notification lists
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * static additional sites (stealth servers)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt * dynamically leared sites (soa queries)
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt Zones also have versions associated with them, each of which, with
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt the exception of the current zone, has an expiry date.
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt "How long are we going to keep them operationally?"
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt While there are expriry dates based on last update /
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt change time + expire. In practice holding the deltas
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt for a few refresh periods should be enough. If the network
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt and servers are up one is enough.
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt "How are we going to generate them from a master file?"
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt UPDATE should not be the only answer to this question.
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt We need a tool that takes the current zone & new zone.
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt Verifies the new zone, generates a delta and feeds this
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt at named. It could well be part of ndc but does not have
801707fe19600313a0b1f7845a518100f69e58b6Evan Hunt Zones need to have certain operations performed on them. The need to