SUMMARY: in.named causing reboot

From: Damon LaCaille (
Date: Tue Jun 16 1998 - 10:25:14 CDT

Original question was as follows:


We have two sparc 5's acting as primary and secondary DNS servers (among
other functions) at our organization for internal name resolution. The
primary is running Solaris 2.5.1, the secondary is running 2.5. They are
both running in.named version 4.9.3-P1 (standard from install).

The problem is that both servers are experiencing random reboots, the last
time it happened was when we restarted the in.named daemon on the primary.
I've turned on debug mode (level 2) and was perusing the /var/tmp/
file but couldn't see any errors in it. The secondary was experiencing
constant reboots for over 12 hours (approximately 1 reboot every 5
minutes), while the primary has experienced a reboot once every 24-72
hours. No other sparc systems are experiencing this symptom in our
environment, so I can only assume the problem would be connected to DNS
somehow. We do, however, have one other machine (an Enterprise 6000) that
has experienced one reboot in the last week, though it is not a DNS server.

Is there a more detailed log file I can use to find out what is happening?
Any help is appreciated, and I will summarize immediately.

Damon LaCaille


I'm not sure if it's fixed yet, we will have to watch the system. The
recommendation was to install BIND version 8.1.2 or 4.9.7 because they both
fix several security and memory problems. However, after downloading and
compiling the 8.1.2 source code, I found the conversion process a little
too daunting to be a one day fix, so I've taken that task to our lab to
start integrating it. In the meantime, I've downloaded SunSolve Patch #
103667-10 which is described below:


Patch-ID# 103667-10
Keywords: security DNS CERT BIND 4.9.3 in.named named-xfer
Synopsis: SunOS 5.5: libresolv, in.named, named-xfer, nslookup & nstest patc
Date: Jun/11/98

Solaris Release: 2.5

SunOS Release: 5.5

Unbundled Product:

Unbundled Release:

Relevant Architectures: sparc

BugId's fixed with this patch: 1238679 1247019 1253600 1264386 1265838
4007986 4008451 4018620 4026266 4037068 4038360 4056997 4068577 4071167
4127028 4133571

Changes incorporated in this version: 4068577 4127017 4127028 4133571


Many thanks to:

Joel Turoff <>
Bismark Espinoza <bismark@alta.Jpl.Nasa.Gov>
Karl Vogel <>

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:12:41 CDT