bind-8.2.2-p5 goes catatonic

Gregory J. Schaffer schaffer at
Sun Mar 19 01:04:14 UTC 2000

This is interesting, in that I have seen a similar problem with 8.2.2-P5
on W2K.  The process still is running but resolutions do not work
properly; usually I have to manually kill the process id and restart
named.  I'll dump the db before killing the process next time and let you
know if I see similar problems.


Greg Schaffer
Network Manager
Middle Tennessee State University

On Thu, 16 Mar 2000, Dave Wreski wrote:

> Date: Thu, 16 Mar 2000 12:06:32 -0500 (EST)
> From: Dave Wreski <dave at>
> To: bind-users at
> Subject: bind-8.2.2-p5 goes catatonic
> Hi all.  A month or two ago I reported a problem with bind-8.2.2-p5
> running on Solaris 2.6 where it becomes unable to resolve even common
> domains such as
> Well, this problem has happened again, and this time I was able to dump
> the database.  After looking thru it with my limited experience with
> interpreting the information, I see there is no $ORIGIN entry for
> YAHOO.COM, which really suprised me.
> When trying to resolve, it appears to timeout, and report
> server failed.  Other domains that are not currently in the database
> are capable of being resolved, as are other common domains such as
>  After restarting named, it works fine.
> I have a dump of the database both before and after.  If there was some
> information I could provide to debug this problem further, I would love to
> do it.
> Thanks for any ideas,
> Dave Wreski

More information about the bind-users mailing list