Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!wuarchive!zaphod.mps.ohio-state.edu!math.lsa.umich.edu!math.lsa.umich.edu!emv From: emv@math.lsa.umich.edu (Edward Vielmetti) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: Monitoring your nameserver Message-ID: Date: 17 Aug 90 12:35:04 GMT References: <9008141525.AA27754@sci.ccny.cuny.edu> <7769@gollum.twg.com> Sender: usenet@math.lsa.umich.edu Followup-To: comp.protocols.tcp-ip.domains Organization: University of Michigan Math Dept., Ann Arbor MI. Lines: 30 In-Reply-To: david@twg.com's message of 16 Aug 90 21:19:42 GMT In article <7769@gollum.twg.com> david@twg.com (David S. Herron) writes: >So how do folks arrange to get automatic notification in a timely way >when their nameserver software dies? Answers for diverse hardware >running unix for me, but others may be interested in other cases. A quick hack would be to have a cron job on occasion which either checks for the existance of critical processes & start's 'em up. Or just start's em & lets the processes fight over how many of which kind are to be running. Buuuut.. Ummmm.... I would think that the right way of managing these things would be to embed into them some piece of SNMP (the Simple Network Management Protocol), and then have them all watched over by a network management station which could get traps when the daemons die, arrange to have things restarted, etc etc. This would have the advantage of letting you watch over a bunch of systems from a single vantage point if you wanted to. That said, I must confess that I don't know whether anyone has stuck SNMP into bind (anyone?), whether there's a MIB defined, or anything like that. I know that Sun doesn't ship it in SunOS 4.0.3, and that the DEC Ultrix 4.0 snmp/bind stuff appears to be amenable to such treatment but hasn't been done. --Ed Edward Vielmetti, U of Michigan math dept