New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

John Collins — Tue, 26 Aug 2008 19:14:26 GMT

Just a note that I've seen some weirdness with the DNS pack and ESX.

It seems the new DNS monitors like to spawn a ton of nslookup jobs on windows hosts, as well as more than usual cscript.exe instances. This caused our ESX servers to max out CPU.

I didn't see it until 24 hours after installing the new mp. Any thoughts/suggestions/ideas?

re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

kevinhol — Tue, 26 Aug 2008 19:22:04 GMT

Yes - this is being investigated - and an updated MP will likely be released to address some of these high-CPU issues seen in specific environments. In some cases - the CPU utilization can be quite significant.

re: New DHCP and DNS management packs released for Windows 2000, 2003, and 2008

Tom Brady — Tue, 04 Nov 2008 00:37:01 GMT

Is there any workarounds for the DNS issue yet? Is it recommended to override that rule that is issuing the NSLookups?

re: DNS MP consuming CPU

kevinhol — Tue, 04 Nov 2008 01:15:14 GMT

I dont know of any good workarounds.... some have discussed extending out the monitors that run these scripts, to space out the frequency, and that helping. The updated MP is expected out very soon.

re: DNS MP consuming CPU

Richard Gerrits — Thu, 13 Nov 2008 19:20:40 GMT

In our case, the high CPU is caused by the fact that the nslookup command generates more than 4k of output. (we have about 60 dns-servers)

Because of this, the wshShell.Exec() is hanging in an endless loop.

(while (objExec.Status == 0) {})

Only workaround I can think of, is using a modified nslookup.exe, which limits the output to 4k.