Home
  •  

Microsoft Windows Server DNS GlobalNames NSLookup

Microsoft.Windows.Server.DNS.GlobalNames.NSLookup (UnitMonitor)

Disabled by default.

Knowledge Base article:

Summary

This monitor checks for Windows Server DNS based on Global Names NSLookUp.

Configuration

Interval Seconds: The interval at which this monitor performs a NSLOOKUP.

Script Timeout Seconds: The total time SCOM will allow the script to run before terminating it.

Query Timeout Seconds: Used for the -timeout option of NSLOOKUP.

Query Type: Used for the -querytype option of NSLOOKUP. Acceptable values are: A, CNAME, PTR, NS, or SOA.

Host Name: The host record to be resolved by NSLOOKUP.

Server: The server to which NSLOOKUP should direct the query.

Accept Non Authoritative: Whether or not SCOM should accept a Non-authoritative response to NSLOOKUP.

Causes

NSLOOKUP failed to resolve the host name.

Resolutions

Ensure that the CNAME record exists in the GlobalNames zone, and that the A record that it references is valid.

Additional

This monitor is disabled by default. Before enabling it, ensure that there is a CNAME record in the GlobalNames zone that matches the host name that you are attempting to resolve.

External

http://technet.microsoft.com/en-us/library/cc816610(v=ws.10).aspx

Element properties:

TargetMicrosoft.Windows.Server.DNS.Zone.Global
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledFalse
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.Server.DNS.NSLookup.Monitor
RemotableTrue
AccessibilityPublic
Alert Message
Windows DNS - GlobalNames NSLookup Failed

Warning indicates a failure internal to the monitor.
Critical indicates NSLookup failed.

Please see Health Explorer for details.
RunAsMicrosoft.Windows.Server.DNS.ActionAccount

Source Code:

<UnitMonitor ID="Microsoft.Windows.Server.DNS.GlobalNames.NSLookup" Accessibility="Public" Enabled="false" Target="Microsoft.Windows.Server.DNS.Zone.Global" ParentMonitorID="Health!System.Health.AvailabilityState" Remotable="true" Priority="Normal" RunAs="Microsoft.Windows.Server.DNS.ActionAccount" TypeID="Microsoft.Windows.Server.DNS.NSLookup.Monitor" ConfirmDelivery="true">

  <Category>AvailabilityHealth</Category>

  <AlertSettings AlertMessage="Microsoft.Windows.Server.DNS.GlobalNames.NSLookup_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="UIGeneratedOpStateId2e9fa13822f445ffb398f55d314ebe09" MonitorTypeStateID="Success" HealthState="Success"/>

    <OperationalState ID="UIGeneratedOpStateIdf73958a4b65c4320aba7088fb09d9f0c" MonitorTypeStateID="InternalScriptError" HealthState="Warning"/>

    <OperationalState ID="UIGeneratedOpStateIdfbc80dcc4dd9448ba2046e51abbc23b0" MonitorTypeStateID="QueryFailure" HealthState="Error"/>

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>900</IntervalSeconds>

    <ScriptTimeoutSeconds>300</ScriptTimeoutSeconds>

    <QueryTimeoutSeconds>10</QueryTimeoutSeconds>

    <QueryType>CNAME</QueryType>

    <HostName>PlaceHolder</HostName>

    <Server>127.0.0.1</Server>

    <AcceptNonAuthoritative>true</AcceptNonAuthoritative>

  </Configuration>

</UnitMonitor>