Home
  •  

Microsoft Windows Server DNS IP Address NSLookup

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

Tests each IP address the server is bound to

Knowledge Base article:

Summary

A DNS server can be bound to listen on multiple IP addresses. This monitor tests each individual IP address for the PTR record 127.0.0.1 which should succeed regardless of whether or not the server has any zones and/or forwarders configured.

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 127.0.0.1

Resolutions

Ensure that the DNS server is started and bound to listen on all IP addresses or the IP address that this monitor is targeting.

Element properties:

TargetMicrosoft.Windows.Server.DNS.Server.IPAddress
Parent MonitorSystem.Health.AvailabilityState
CategoryAvailabilityHealth
EnabledTrue
Alert GenerateTrue
Alert SeverityMatchMonitorHealth
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeMicrosoft.Windows.Server.DNS.NSLookup.Monitor
RemotableTrue
AccessibilityPublic
Alert Message
Windows DNS - NSLookup Failed Against a Local Address

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.IPAddress.NSLookup" Accessibility="Public" Enabled="true" Target="Microsoft.Windows.Server.DNS.Server.IPAddress" 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.IPAddress.NSLookup_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

  </AlertSettings>

  <OperationalStates>

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

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

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

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>901</IntervalSeconds>

    <ScriptTimeoutSeconds>300</ScriptTimeoutSeconds>

    <QueryTimeoutSeconds>10</QueryTimeoutSeconds>

    <QueryType>PTR</QueryType>

    <HostName>127.0.0.1</HostName>

    <Server>$Target/Property[Type="Microsoft.Windows.Server.DNS.Server.IPAddress"]/IPAddress$</Server>

    <AcceptNonAuthoritative>true</AcceptNonAuthoritative>

  </Configuration>

</UnitMonitor>