Note: This is an archival copy of Security Sun Alert 200536 as previously published on
Latest version of this security advisory is available from as Sun Alert 1000408.1.
Article ID : 1000408.1
Article Type : Sun Alerts (SURE)
Last reviewed : 2004-07-26
Audience : PUBLIC
Copyright Notice: Copyright © 2010, Oracle Corporation and/or its affiliates.

The in.named(1M) Process May Die Upon Receiving Dynamic Updates


Release Phase

Solaris 8 Operating System

Bug Id

Date of Resolved Release


A remote privileged user may be able to create a denial of the Domain Name System (DNS) service by killing the in.named(1M) daemon. As a result, applications, systems and devices relying on DNS may fail.

Contributing Factors

This issue can occur in the following releases:

SPARC Platform

  • Solaris 8 without patch 109326-16

x86 Platform

  • Solaris 8 without patch 109327-16

Note: Solaris 7 and Solaris 9 are not affected by this issue.

The described issue only occurs on systems configured as an Internet DNS server. A system is configured to be a DNS server if the configuration file "/etc/named.conf" (named.conf(4)) exists.


If the described issue occurs, the in.named(1M) process is no longer running. To determine if the in.named(1M) process is running, use the pgrep(1) command as shown:

    $ pgrep in.named || echo "in.named process NOT found!"

Messages may be logged to syslog(3c) with a severity of "LOG_NOTICE" whose content starts with the following:

    "unapproved update from"


To work around the described issue, restart in.named(1M) using the following command as root user:

    # pgrep in.named || /usr/sbin/in.named

The following simple Bourne shell script will check and restart in.named(1M) as necessary:

    # while pgrep in.named || /usr/sbin/in.named; do sleep 10; done


This issue is addressed in the following releases:

SPARC Platform

  • Solaris 8 with patch 109326-16 or later

x86 Platform

  • Solaris 8 with patch 109327-16 or later

Modification History



This solution has no attachment