HATHAWA@gecrdvm1.crd.ge.com (Barry Hathaway) (09/25/90)
I hope that this is the correct list for questions/problems relating to BIND.
If not please let me know.
I'm trying to bring up a name server for an internal class A network so it
should be authoritative for root. The file that named.boot reads for the
zone appears below:
$ORIGIN crd.ge.com
.. IN SOA crdns hathawa.gecrdvm1.crd.ge.com (
0465 ; Serial
86400 ; Refresh
600 ; Retry
864000 ; Expire
86400) ; Minimum
IN NS crdns
snoopy IN A 3.1.4.1
snoopy IN MX 0 snoopy
*****other A and MX records for other hosts deleted *****
As named reads the file it gives me the following errors:
Debug turned ON, Level 5
Version = named 4.8 #1: Mon Sep 24 16:17:42 EDT 1990
hathawa@crdns:/usr/users/hathawa/bind.4.8/named
bootfile = /etc/named.boot
ns_init(/etc/named.boot)
savehash GROWING to 2
savehash GROWING to 2
zone[1] type 1: '.', source = root.zone
db_load(root.zone, , 1)
db_load: origin crd.ge.com, buf
db_load: origin now crd.ge.com
Line 2: Unknown type: ..
root.zone: line 2: database format error ('.', 0)
root.zone: line 4: database format error ('', 465)
root.zone: line 6: database format error ('', 600)
root.zone: line 8: database format error ('', 86400)
d='snoopy.crd.ge.com', c=1, t=1, ttl=0, data='3.1.4.1'
db_update(snoopy.crd.ge.com, 0x10013a20, 0x10013a20, 01, 0x100139c0)
savehash GROWING to 2
savehash GROWING to 2
It does not seem to matter whether I running bind 4.8 or the Ultrix-supplied
one; however, IBM's VM name server is perfectly happy with the file.
Any ideas.?cricket@WINNIE.CORP.HP.COM ("Cricket") (09/26/90)
I'm trying to bring up a name server for an internal class A
network so it should be authoritative for root. The file that
named.boot reads for the zone appears below:
$ORIGIN crd.ge.com
.. IN SOA crdns hathawa.gecrdvm1.crd.ge.com (
0465 ; Serial
86400 ; Refresh
600 ; Retry
864000 ; Expire
86400) ; Minimum
IN NS crdns
snoopy IN A 3.1.4.1
snoopy IN MX 0 snoopy
(I'm assuming that somewhere in named.boot you have a line like
primary . <file excerpted above>
which sets the ORIGIN to "root" before you explicitly set the ORIGIN
to crd.ge.com. I'm also assuming that you don't really want "crdns"
to be known as "crdns" - a top-level domain - but rather as
"crdns.crd.ge.com".)
As named reads the file it gives me the following errors:
Debug turned ON, Level 5
Version = named 4.8 #1: Mon Sep 24 16:17:42 EDT 1990
hathawa@crdns:/usr/users/hathawa/bind.4.8/named
bootfile = /etc/named.boot
ns_init(/etc/named.boot)
savehash GROWING to 2
savehash GROWING to 2
zone[1] type 1: '.', source = root.zone
db_load(root.zone, , 1)
db_load: origin crd.ge.com, buf
db_load: origin now crd.ge.com
Line 2: Unknown type: ..
root.zone: line 2: database format error ('.', 0)
root.zone: line 4: database format error ('', 465)
root.zone: line 6: database format error ('', 600)
root.zone: line 8: database format error ('', 86400)
d='snoopy.crd.ge.com', c=1, t=1, ttl=0, data='3.1.4.1'
db_update(snoopy.crd.ge.com, 0x10013a20, 0x10013a20, 01, 0x100139c0)
savehash GROWING to 2
savehash GROWING to 2
Looks like the ".." in the SOA is giving you problems. I can
understand why it might - I've never seen it before in my DNS life.
Maybe it's IBM value-added? ;-) Certainly wouldn't enhance
portability of db files between implementations....
If what you're trying to do is make crdns authoritative for the root,
this oughta do it:
@ in soa crdns.crd.ge.com. hathawa.gecrdvm1.crd.ge.com (
0465 ; Serial
86400 ; Refresh
600 ; Retry
864000 ; Expire
86400) ; Minimum
in ns crdns.crd.ge.com.
(other RRs)
If I'm inferring what you're trying to do correctly (include "snoopy"
under crd.ge.com), then you probably should include that in a
separate db file for crd.ge.com. Add another line to /etc/named.boot:
primary crd.ge.com db.crd
(or "secondary" - I don't know how you're set up). The default
ORIGIN in db.crd will be crd.ge.com and you can refer to "snoopy"
simply as "snoopy":
snoopy in a 3.1.4.1
snoopy in mx 0 snoopy.crd.ge.com.
cricket
hostmaster@hp.com