Home
  •  

NLS DNS entry invalid

AP.Remote.Access.Monitor.DA_NLS_HEURISTIC_INVALID_DNS_ENTRY (UnitMonitor)

The network location server does not have a valid DNS entry. DirectAccess clients located in the corporate network will not be able to resolve the server name, and internal network connectivity will not work as expected.

Knowledge Base article:

Summary

The network location server does not have a valid DNS entry. DirectAccess clients located in the corporate network will not be able to resolve the server name, and internal network connectivity will not work as expected.

Causes

1. There is no valid DNS entry for the network location server.

2. DirectAccess settings for the network location server are not configured correctly.

Resolutions

1. Ensure enterprise DNS servers can resolve the name of the network location server.

2. Enable fallback to local name resolution in the Remote Access Setup Wizard.

3. Verify connectivity to the DNS server, and check DNS server settings.

Note: Operations status is updated in accordance with the configured refresh interval. Clicking Refresh to manually update status does not update the status of the DNS resolution and ICMP reachability checks.

Element properties:

TargetAP.Remote.Access.Class.NetworkLocationServer
Parent MonitorSystem.Health.ConfigurationState
CategoryCustom
EnabledTrue
Alert GenerateTrue
Alert SeverityError
Alert PriorityNormal
Alert Auto ResolveTrue
Monitor TypeAP.Remote.Access.Monitor.HeuristicMonitorType
RemotableTrue
AccessibilityPublic
Alert Message
NLS DNS entry invalid

Error Description - {0}
Error Cause - {1}
Error Resolution - {2}
RunAsDefault

Source Code:

<UnitMonitor ID="AP.Remote.Access.Monitor.DA_NLS_HEURISTIC_INVALID_DNS_ENTRY" Accessibility="Public" Enabled="true" Target="AP.Remote.Access.Class.NetworkLocationServer" ParentMonitorID="Health!System.Health.ConfigurationState" Remotable="true" Priority="Normal" TypeID="AP.Remote.Access.Monitor.HeuristicMonitorType" ConfirmDelivery="true">

  <Category>Custom</Category>

  <AlertSettings AlertMessage="AP.Remote.Access.Monitor.DA_NLS_HEURISTIC_INVALID_DNS_ENTRY_AlertMessageResourceID">

    <AlertOnState>Warning</AlertOnState>

    <AutoResolve>true</AutoResolve>

    <AlertPriority>Normal</AlertPriority>

    <AlertSeverity>Error</AlertSeverity>

    <AlertParameters>

      <AlertParameter1>$Data/Context/DataItem/Property[@Name='ErrorDesc']$</AlertParameter1>

      <AlertParameter2>$Data/Context/DataItem/Property[@Name='ErrorCause']$</AlertParameter2>

      <AlertParameter3>$Data/Context/DataItem/Property[@Name='ErrorResolution']$</AlertParameter3>

    </AlertParameters>

  </AlertSettings>

  <OperationalStates>

    <OperationalState ID="DA_NLS_HEURISTIC_INVALID_DNS_ENTRY_Error" MonitorTypeStateID="Error" HealthState="Error"/>

    <OperationalState ID="DA_NLS_HEURISTIC_INVALID_DNS_ENTRY_Warning" MonitorTypeStateID="Warning" HealthState="Warning"/>

    <OperationalState ID="DA_NLS_HEURISTIC_INVALID_DNS_ENTRY_Success" MonitorTypeStateID="Healthy" HealthState="Success"/>

  </OperationalStates>

  <Configuration>

    <Interval>300</Interval>

    <SyncTime/>

    <ComponentName>Network Location Server</ComponentName>

    <HeuristicId>2148335619</HeuristicId>

    <Debug>false</Debug>

  </Configuration>

</UnitMonitor>