Adrian C

7 Feb 2011 1:39 PM

Hello,

At my server this allert is generated when the Local Resolution time gets a 0 ( zero ) value!

Any ideeas?

Br,

Adrian

Noel F

17 Mar 2011 1:37 AM

Hey guys, I've installed the new Windows 2008/R2 DNS Management Pack (v6.0.7000.0) and I'm still getting the same problem. Could it be that Windows 2008 R2 still isn't fully supported in the new MP? Anyway - for your records and so this is all linked, I've created a TechNet Forum post here with the issue: social.technet.microsoft.com/.../54f35d15-e004-45b1-8e9c-444fa30cdb59

Hopefully this can be resolved.

Rajasekhar

26 Jan 2013 7:35 AM

Can we ignore the below scom alert. any idea

Alert: DNS 2008/R2 Resolution Time Alert Priority: 1 Severity: 2 Resolution state: New

Ram Kumar

19 Feb 2013 5:12 PM

Hi Kevin,

I need to monitor DNS 2000 zone, but i am using the latest MP for DNS management pack. Could you please let me know how to monitor this.

Thanks in advance.

Darshan G. Parab

19 Aug 2013 8:19 AM

This may sound strange.. But what if I'm getting this alert from my WSUS?

Dwayne R

25 Nov 2014 12:24 AM

I know its a bit late but in Adrian's case look for errors in the event logs for the agent (event 1163). You may find that its reporting the DNS server is stopped on ongoing 0 second responses. This may or may not be correct.

I had the same issue the DNS server was responding quickly all the time (windows 2003), SCOM showed 0 second responses all the time, and the event logs showed the DNS service without issue, BUT the operations manager logs showed DNS to be stopped (i.e event 1163 : DNS Server Resolution Check : The DNS service is not running. Monitoring script cannot continue.)

The trick is to workout why its not working, so once again where possible extract what the monitor is actually doing and duplicate.

In my case trying the nslookup via the NslookupAllTests.js script took forever, ie 20 minutes later its still running, and we were seeing alerts for it doing so. So I had to look there to find the real problem

Nile

15 Jan 2015 10:10 PM

Here is another take at this issue elsewhere, basically DNS listens on ipv4 and v6 ifaces. And if you don't have both reverse and forward zones config-ed - which is usually how your ipv6 will look... this causes the delays and extra noise. Two ways to resolve, by either turning off Listening on Ipv6 or creating zones to accomodate the monitoring script.