Home
  •  

Microsoft Windows Server DNS WINSR NSLookup

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

Disabled by default

Knowledge Base article:

Summary

The NetBIOS protocol was the principal network protocol that early versions of Windows used. In conjunction with Windows Internet Name Service (WINS), NetBIOS supports a simple, nonhierarchical naming system. You can configure DNS servers and clients to support NetBIOS and WINS as a supplement to the Domain Name System (DNS) protocol.

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 WINS server(s) configured for the DNS server are available and contain the record the monitor is attempting to resolve.

Additional

This monitor is disabled by default. Before enabling it, a record should be created on the WINS server(s) that contains the host name being tested.

Element properties:

TargetMicrosoft.Windows.Server.DNS.Zone.WINSRConnector
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 - WINS-R 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.WINSR.NSLookup" Accessibility="Public" Enabled="false" Target="Microsoft.Windows.Server.DNS.Zone.WINSRConnector" 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.WINSR.NSLookup_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>MatchMonitorHealth</AlertSeverity>

  </AlertSettings>

  <OperationalStates>

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

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

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

  </OperationalStates>

  <Configuration>

    <IntervalSeconds>900</IntervalSeconds>

    <ScriptTimeoutSeconds>300</ScriptTimeoutSeconds>

    <QueryTimeoutSeconds>10</QueryTimeoutSeconds>

    <QueryType>PTR</QueryType>

    <HostName>4.3.2.1.in-addr.arpa</HostName>

    <Server>127.0.0.1</Server>

    <AcceptNonAuthoritative>true</AcceptNonAuthoritative>

  </Configuration>

</UnitMonitor>