DNS service Element always reports false down

I have loaded the DNS service element module on a Solaris 10 DNS server running SMC 3.6.1. There is nothing special about the DNS server it's running the version Bind that came with Solaris 10 6/06 and it's being controlled via SMF. Bind is listening to port 53 on all interfaces and I am able to resolve queries both locally and from other machines.

The DNS service element finds the process and shows one instance of named running in the Process Details table but reports the availability as down in the Server Details table. I've added a row to the Service Measurement Table and that fails as well.

I've done everything I can think of to make sure SMC can access port 53 on any interface it chooses and I know the server is responding properly to requests. Anybody have an idea as to why it's still reporting the service as down?

[856 byte] By [wks9326a] at [2007-11-26 14:09:07]
# 1

Hi Wks9326,

> The DNS service element finds the process and shows

> one instance of named running in the Process Details

> table but reports the availability as down in the

> Server Details table. I've added a row to the

> Service Measurement Table and that fails as well.

I'm not positive, but I seem to remember the DNS module tests availability by asking bind to resolve it's own hostname. Can you resolve the hostname of the system running the DNS module?

I'm not sure: just guessing: something else to try...

Regards,

Mike.Kirk@HalcyonInc.com

http://www.HalcyonInc.com

Mike-Kirka at 2007-7-8 1:56:00 > top of Java-index,Administration Tools,Sun Management Center...
# 2
Thank you that was exactly what I wanted to know. I don't know why Sun doens't put information like that in the documentation.
wks9326a at 2007-7-8 1:56:00 > top of Java-index,Administration Tools,Sun Management Center...