It could be late but I fail to see how this is related to SMF. zones-discuss would probably be more appropriate?
-tony Mahendra Prabhu wrote: > Hello all, > > Customer use a formal change management process for adds/changes/deletes to > the resource records in the Nominum ANS DNS. > The change management process requires a backout plan should a change > that has been made go wrong. > > With BIND we simply copied the existing zone file to a backup location > somewhere, then edited the existing file (incrementing serial No) and > then restarted named. If a backout was then required we simply copied > the original zone file back, increased the serial number by two and > restarted named. Then it was back to the way it was before we started > any change. > > With Nominum ANS we have been using the "ans_edit zone" command to > change resource records. Our current backout would be to perform another > "ans_edit zone" and manually reverse the changes. This is all very well > but if there are a lot of changes, or in editing with vi a whole lot of > resource records accidentally get deleted and written back, what do we > do? > > It would be nice to enter a command to make the zone go back to a > previous revision number and at the same time incrementing the serial > number so it is then the latest > Regards, > Prabhu. > > -- > <http://www.sun.com/solaris> * Mahendra Prabhu * > APAC System TSC (PTS) - Solaris Operating Environment > > *Sun Microsystems, Inc. India* > Phone x50072/+91 80 56913 072 > Email Mahendra.Prabhu at Sun.COM <mailto:Mahendra.Prabhu at Sun.COM> > <http://www.sun.com/solaris> > > ------------------------------------------------------------------------ > > _______________________________________________ > smf-discuss mailing list > smf-discuss at opensolaris.org >
