Joshua.R.Poulson@CYBER.WIDENER.EDU (10/02/90)
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-----
Any advice or directions for further reading would be greatly appreciated.
The machine I'm using (if it matters, which I doubt) is a PS/2 Model 80
running AIX PS/2. The only restriction listed in the manual is that it
supports the "IN" type only.
Thanks in advance everybody.
--JRP [Joshua.R.Poulson@cyber.Widener.EDU] [Josh Poulson]pvm@VENERA.ISI.EDU (Paul Mockapetris) (10/02/90)
> 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
Joshua.R.Poulson@CYBER.WIDENER.EDU (10/03/90)
Well, the results are in.
There were quite a few things wrong with my named.db and I owe thanks to the
following people:
kjd@mold.enet.dec.com
pvm@venera.isi.edu
cricket@winnie.corp.hp.com
map@gaak.LCS.MIT.EDU
ARIEL@RELAY.PRIME.COM
mdb@ESD.3Com.COM
dan@sci.ccny.cuny.edu
and one other individual whose mail message was accidentally deleted (sorry).
The new, improved, and operative named.db (for those who are wondering):
$ORIGIN Widener.EDU.
@ IN SOA aixps2.Widener.EDU. jrp.aixps2.Widener.EDU. (
20 ; Serial
3600 ; Refresh
600 ; Retry
3600000 ; Expire
172800 ) ; Minimum
IN NS aixps2.Widener.EDU.
aixps2 IN MX 100 aixps2.Widener.EDU.
IN A 192.55.239.55
cyber IN MX 100 cyber.Widener.EDU.
IN A 192.55.239.13
The changes are numerous:
# Addition of a period to the end of the $ORIGIN.
# Addition of "IN" to almost all of the stanzas.
# Addition of a contact for the SOA record.
# A space before the end ')' in the SOA record.
# A much larger minimum for the SOA (not required, but recommended)
# Addition of arguments for MX records.
Thank you everyone.
Special thanks to kjd@mold.enet.dec.com for help with the BIND manual.
--JRP [Now I must fix the named.boot file...]