Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!uwm.edu!bionet!agate!ucbvax!SH.CS.NET!jcurran From: jcurran@SH.CS.NET (John Curran) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: bad .edu records from jackson state Message-ID: <9104040918.AA01515@ucbvax.Berkeley.EDU> Date: 3 Apr 91 10:35:56 GMT References: <1991Apr2.034854.2720@noc.sura.net> Sender: usenet@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 25 -------- From: dave o'leary > A couple of comments on the situation - first, it is not a good thing > that a site's misconfiguration can screw things up so badly. > Supporting efforts to improve bind, etc. and encouraging everyone to > run up to date software are noble activities. On the positive side, experiences like this tend to improve the tolerance of many bind implementations as sites quickly move to insert logging and filtering. In time, we can expect these ad-hoc changes to prevent major DNS outages, right? :-) > Also, the documentation on how to set up this stuff correctly > (hints on what to do and what *not* to do) should be more accessable > (do they exist at all?). I get the impression that it depends on where you are. I know several regionals that provide DNS training and/or setup to sites, but I don't think that's standard on most nets. In terms of documentation, there are quite a few DNS presentations around (slides with bullets), but I'm not aware of any text writeups besides the Berkley BIND supplementry doc, and each vendors subsequent rewrite of it. /John