Problems moving to 9.3.0

Hi,

Moving from BIND 9.2.3 to 9.3.0, I've been seeing some problems. On a
PowerPC NetBSD 2.0 system on which 9.2.3 works perfectly, I get this from
9.3.0:

Oct 20 17:04:54 lain named[368]: rbt.c:1584: INSIST(child != (void *)0) failed
Oct 20 17:04:54 lain named[368]: exiting (due to assertion failure)

I've now set up another PowerPC NetBSD 2.0 machine since I've had to
revert to 9.2.3 on the colocated machine, and I've narrowed the problem
down to where I realize that I cannot have a domain name in named.conf
which is the same as the domain name used in my hostname. It could be
something else, but I'm at a loss:

winona: {159} hostname
winona.ziaspace.com
winona: {160} tail -n 5 named.conf
zone "ziaspace.com" {
type master;
allow-transfer { slaves; };
file "db.ziaspace.nl";
};
winona: {161} /etc/rc.d/named9 start
Starting named.
winona: {162} tail -n 5 /var/log/messages
Nov 22 22:44:29 winona named[11118]: zone ziaspace.com/IN: loaded serial 2004112100
Nov 22 22:44:29 winona named[11118]: running
Nov 22 22:44:29 winona named[11118]: zone ziaspace.com/IN: sending notifies (serial 2004112100)
Nov 22 22:44:29 winona named[11118]: rbt.c:1617: INSIST(child != (void *)0) failed
Nov 22 22:44:29 winona named[11118]: exiting (due to assertion failure)
winona: {163} vi named.conf
(changed file)
winona: {164} tail -n 5 named.conf
zone "ziaspace.nl" {
type master;
allow-transfer { slaves; };
file "db.ziaspace.nl";
};
winona: {165} /etc/rc.d/named9 start
Starting named.
winona: {166} tail -n 5 /var/log/messages
Nov 22 22:46:20 winona named[15469]: command channel listening on 127.0.0.1#953
Nov 22 22:46:20 winona named[15469]: command channel listening on ::1#953
Nov 22 22:46:20 winona named[15469]: zone ziaspace.nl/IN: loaded serial 2004112100
Nov 22 22:46:20 winona named[15469]: running
Nov 22 22:46:20 winona named[15469]: zone ziaspace.nl/IN: sending notifies (serial 2004112100)

So what is so special about ziaspace.com as opposed to ziaspace.nl?


The other problem I'm having is with a NetBSD 1.6.2 machine and BIND
9.3.0. When I launch it, I see this in the logs:

Oct 20 11:24:55 grittykitty named[19879]: starting BIND 9.3.0 -u named -t /var/chroot/named -c /etc/namedb/named.conf
Oct 20 11:24:55 grittykitty named[19879]: loading configuration from '/etc/namedb/named.conf'
Oct 20 11:24:55 grittykitty named[19879]: listening on IPv6 interfaces, port 53
Oct 20 11:24:55 grittykitty named[19879]: listening on IPv4 interface rtk0, 67.101.178.13#53
Oct 20 11:24:55 grittykitty named[19879]: listening on IPv4 interface rtk1, 192.168.10.1#53
Oct 20 11:24:55 grittykitty named[19879]: listening on IPv4 interface tlp0, 192.168.20.1#53
Oct 20 11:24:55 grittykitty named[19879]: listening on IPv4 interface lo0, 127.0.0.1#53
Oct 20 11:24:56 grittykitty named[19879]: loading configuration: unexpected end of input
Oct 20 11:24:56 grittykitty named[19879]: exiting (due to fatal error)

The named.conf on that machine has run fine with 9.2.3 for ages, and it's
identical to the configuration files on three other machines, including
another 1.6.2 PowerPC machine. named-checkconf reports nothing.

So my question is this: if named-checkconf doesn't report anything, and I
can run the same named.conf elsewhere, then how to do I get more detailed
a report of BIND's problem so I can see what going on? I corrected the
problem by removing some excess whitespace, but it's not helpful that
named-checkconf doesn't have the same rules for what will and what won't
work as BIND. Ideas?

Thanks,
John Klos
ZiaSpace Productions