I think the clue in the log is that I made the change on the 19th. I discovered that the service was enabled on the 21st. So if I read the log messages correctly, its state went like this;
restart->:kill->disabled I've seen similar behavior in the past, where the DNS server would be considered "disabled" after a reboot when the service was very much "enabled" during the previous boot. I haven't seen this kind of behavior with other SMF services. To my knowledge there are no configuration problems with BIND or named in particular. Thanks. This message posted from opensolaris.org
