Bind keeps dying!

[Benjamin Donnachie]

I am using bind 9.2.5 on a server running Fedora Core 3 and lately named =
has
started dying with=20
assertion errors - normally during start up, but can be at almost any time
after too:

The most recent one from this morning:

Aug 25 17:02:39 gavin named: named startup succeeded
Aug 25 17:02:45 gavin named[2968]: message.c:2086: REQUIRE(name !=3D =
((void
*)0) &&
*name =3D=3D ((void *)0)) failed
Aug 25 17:02:45 gavin named[2968]: exiting (due to assertion failure)

... and previous logwatch notifications:

--------------------- Named Begin ------------------------=20
**Unmatched Entries**
    failed: 8 Time(s)
    succeeded: 3 Time(s)
    succeeded : 1 Time(s)
   master.c:1105: INSIST(new_in_use < 4) failed: 1 Time(s)
   mem.c:1021: REQUIRE((((ctx) !=3D ((void *)0)) && (((const isc__magic_t
*)(ctx))->magic =3D=3D ((('M') << 24 | ('e') << 16 |
('m') << 8 | ('C')))))) failed: 1 Time(s)
   message.c:2086: REQUIRE(name !=3D ((void *)0) && *name =3D=3D ((void =
*)0))
failed: 2
Time(s)
   named startup failed: 2 Time(s)
   rdata.c:409: REQUIRE((((target)->flags & ~0x0001) =3D=3D 0)) failed: 1
Time(s)
   view.c:413: REQUIRE((((view) !=3D ((void *)0)) && (((const isc__magic_t
*)(view))->magic =3D=3D ((('V') << 24 | ('i') << 16 |
('e') << 8 | ('w')))))) failed: 3 Time(s)

 ---------------------- Named End -------------------------=20


I use named as a caching dns server, with extra entries for the internal
network.

A web search has drawn a blank, and I haven't been able to find anything =
on
the bind website. =20
Has anyone got any ideas why this keeps happening?   This error used to be
extremely rare but is=20
now happening increasingly often - Is there a known issue with bind?  =
Could
there be a problem=20
with my setup?

Here's my named.conf file:

//
// named.conf for Red Hat caching-nameserver=20
//

options {
        directory "/var/named";
        dump-file "/var/named/data/cache_dump.db";
        statistics-file "/var/named/data/named_stats.txt";
        /*
         * If there is a firewall between you and nameservers you want
         * to talk to, you might need to uncomment the query-source
         * directive below.  Previous versions of BIND always asked
         * questions using port 53, but BIND 8.1 uses an unprivileged
         * port by default.
         */
         // query-source address * port 53;
};

//=20
// a caching only nameserver config
//=20
controls {
        inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};


// Router only supports dyndns, so cheat and redirect to no-ip.
zone "members.dyndns.org" {
        type master;
        file "redirect.db";
        allow-update { none; };
};


zone "pythagoras.no-ip.org" {
        type master;
        file "pythagoras_no-ip_org.db";
        allow-update { localhost; };
};

zone "0.168.192.in-addr.arpa" IN {
        type master;
        file "rev.pythagoras_no-ip_org.db";
        allow-update { localhost; };
};

zone "." IN {
        type hint;
        file "named.ca";
};

zone "localdomain" IN {
        type master;
        file "localdomain.zone";
        allow-update { none; };
};

zone "localhost" IN {
        type master;
        file "localhost.zone";
        allow-update { none; };
};

zone "0.0.127.in-addr.arpa" IN {
        type master;
        file "named.local";
        allow-update { none; };
};

zone
"0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" =
IN
 {
        type master;
        file "named.ip6.local";
        allow-update { none; };
};

zone "255.in-addr.arpa" IN {
        type master;
        file "named.broadcast";
        allow-update { none; };
};

zone "0.in-addr.arpa" IN {
        type master;
        file "named.zero";
        allow-update { none; };
};

include "/etc/rndc.key";

I should be very grateful for any assistance with this matter.


--
Benjamin
benjamin at pythagoras.no-ip.org