Hi,
Our customers are receiving bogus DNS resolution failure alerts though the site is rendering fine from the watcher node.Nslookup shows the name resolves after first or 2nd timeout and this behavior is expected in some of our internal name space that have a long resolution path.Is SCOM perform an nslookup first?What is the default DNS resolution time SCOM use? I'm trying to set higher threshold for DNS Resolution time in custom monitor to mitigate this.Users doesn't want to disable the DNS resolution monitor and looking for a permanent fix.This issue has been going on a while in our environment. Any help would be much appreciated. Our SCOM is 2012 sp1 CU4.
C:\Users\admin>nslookup xxxxServer: abc.contosso.com
Address: 10.4.5.6
Non-authoritative answer:
DNS request timed out.
timeout was 2 seconds.
Name: abc.xyz.contosso.com
Address: 10.2.3.4
Aliases: abc.xyx.contosso.com
Thanks,