Bind 8.2.2-P5 stops on Solaris 2.6

[Kevin Darcy]

Offhand, it looks like maybe named's listen-on data structure is getting
munged somehow, followed shortly thereafter by an abrupt crash. Is it
leaving a core file? Perhaps you should submit a bug report to ISC.


- Kevin

Hans J Jakobsen wrote:

> I am having problems with bind stops running.
> When running with -d 2 the last output is:
>
> ....
> ns_req: answer -> [127.0.0.1].43056 fd=20 id=27125 size=213 rc=0
> Cleaned cache of 1 RRset
> getnetconf(generation 954254648)
> getnetconf: SIOCGIFCONF: ifc_len = 64
> getnetconf: considering lo0 [127.0.0.1]
> dup interface addr [127.0.0.1].53 (lo0)
> getnetconf: considering hme0 [x.x.x.197]
> dup interface addr [x.x.x.197].53 (hme0)
>
> $ ifconfig -a
> lo0: flags=849<UP,LOOPBACK,RUNNING,MULTICAST> mtu 8232
>         inet 127.0.0.1 netmask ff000000
> hme0: flags=863<UP,BROADCAST,NOTRAILERS,RUNNING,MULTICAST> mtu 1500
>         inet x.x.x.197 netmask ffffffe0 broadcast x.x.x.223
> $ uname -a
> SunOS x 5.6 Generic_105181-17 sun4u sparc SUNW,Ultra-4
>
> Partial configuration file:
> options {
>         directory "/etc/named_dir";
>         forward only;
>         forwarders {
>                 q.q.q.q;
>                 z.z.z.z;
>         };
>          query-source address * port 53;
> };
>
> zone "0.0.127.IN-ADDR.ARPA" {
>         type master;
>         file "db.127.0.0";
> };
>
> zone "internal.zzz.com" {
>         type slave;
>         file "db.zzz.internal";
>         masters {
>                 y.y.y.y;
>         };
> and more like that
>
> /hjj
> --
> Hans Jørgen Jakobsen