DNS proxy failure

DNS_proxy_failure_1_Rule (Rule)

Knowledge Base article:

Management Pack
Summary
The DNS proxy agent component of Network Address Translation (NAT) protocol encountered an error.
 
Causes
The most common reasons for this error are:
  1. Network address translation was enabled on the interface.
  2. The agent failed to register with local DNS and WINS servers for changes.
  3. The agent failed to read the list of name-resolution servers from the registry.
  4. The agent couldn't resolve a query even after consulting all the name-resolution servers.
  5. The agent couldn't resolve a query as there is no name-resolution server configured and no interface is configured as default for name resolution.
 
Resolutions
  1. Verify the configuration on the interface.
  2. If the server is low on memory, take appropriate action to increase the available memory. See Help and Support Center for information on low memory.
  3. Configure one or more name-resolution servers or configure an interface as default for name-resolution.
  4. Remove the list of name-resolution servers and reconfigure them.
  5. If the problem persists, Stop and restart the Routing and Remote Access service.
 
Sample Event
Sample Event#1: The DNS proxy agent detected network address translation (NAT) enabledon the interface with index ''%1''.The agent has disabled itself on the interface in order to avoidconfusing clients.
Sample Event#2: The DNS proxy agent was unable to register for notification of changesto the local list of DNS and WINS servers.This may indicate that system resources are low.The data is the error code.
Sample Event#3: The DNS proxy agent was unable to read the local list of name-resolutionservers from the registry.The data is the error code.
Sample Event#4: The DNS proxy agent was unable to resolve a query from %1after consulting all entries in the local list of name-resolution servers.
Sample Event#5: The DNS proxy agent was unable to resolve a querybecause no list of name-resolution servers is configured locallyand no interface is configured as the default for name-resolution.Please configure one or more name-resolution server addresses,or configure an interface to be automatically dialed when a requestis received by the DNS proxy agent.
Sample Event#6: The DNS proxy agent encountered an error while obtaining the local listof name-resolution servers.Some DNS or WINS servers may be inaccessible to clients on the local network.The data is the error code.
Sample Event#7: The DNS proxy agent was unable to read the ICS Domain suffix stringfrom the registry.The data is the error code.
 
© 2004 Microsoft Corporation, all rights reserved.

Element properties:

TargetMicrosoft.Windows.RemoteAccess.2012.Class.VPNServer
CategoryEventCollection
EnabledTrue
Alert GenerateFalse
RemotableTrue
Event LogSystem

Member Modules:

ID Module Type TypeId RunAs 
DS DataSource Microsoft.Windows.EventProvider Default
WriteToDB WriteAction Microsoft.SystemCenter.CollectEvent Default

Source Code:

<Rule ID="DNS_proxy_failure_1_Rule" Enabled="true" Target="Microsoft.Windows.RemoteAccess.2012.Class.VPNServer" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>System</LogName>
<Expression>
<And>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>^(31001|31007|31008|31009|31011|31012|31014)$</Pattern>
</RegExExpression>
</Expression>
<Expression>
<RegExExpression>
<ValueExpression>
<XPathQuery Type="String">PublisherName</XPathQuery>
</ValueExpression>
<Operator>MatchesRegularExpression</Operator>
<Pattern>SharedAccess_NAT|ipnathlp</Pattern>
</RegExExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="WriteToDB" TypeID="SystemCenter!Microsoft.SystemCenter.CollectEvent"/>
</WriteActions>
</Rule>