Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sdd.hp.com!decwrl!ucbvax!VENERA.ISI.EDU!pvm From: pvm@VENERA.ISI.EDU (Paul Mockapetris) Newsgroups: comp.protocols.tcp-ip.domains Subject: Re: What's wrong with this named.db? Message-ID: <9010021559.AA12206@venera.isi.edu> Date: 2 Oct 90 15:58:57 GMT References: <5A0A0209241B0210-MTABWIDENER*Joshua.R.Poulson@cyber.widener.edu> Sender: daemon@ucbvax.BERKELEY.EDU Reply-To: pvm@venera.isi.edu Distribution: inet Organization: The Internet Lines: 47 > I'm getting really confused about the format of the database file for my > nameserver database. What is it that I'm doing wrong? I've read through > piles of RFC's and then consulted the manuals for my machine (absolutely > no help at all...). > > Here's my file > > -----cut here----- > $ORIGIN Widener.EDU > @ IN SOA aixps2.Widener.EDU. ( > 20 ; Serial > 3600 ; Refresh > 600 ; Retry > 3600000; Expire > 60) ; Minimum > NS aixps2.Widener.EDU. > aixps2 MX aixps2.Widener.EDU. > A 192.55.239.55 > cyber MX cyber.Widener.EDU. > A 192.55.239.13 > -----cut here----- > 1. MX needs a preference. Perhaps: aixps2 MX 100 aixps2.Widener.EDU. The 100 is just a value, with lower values being better. Lots of folks use 0 for looping back to the same machine, but I recommend a larger value so that you can slip something in below should you get the urge. 2. Redundant Servers You should have more than one name server to represent your domain. It can be anywhere in the Internet, and should be as independent as possible from aixps2.Widener.EDU, so that a single Ethernet or power failure or network connectivity problem or meteor can't take out both. 3. Increase your minimum Your minimum is 60 seconds or one minute. It should probably be at least two days. This is the only problem that isn't well described in the RFCs. If you don't want to do this, send me private Email and I'll try to convince you. paul