Alert generating rule for Configuration.
The DNS server configuration consists of the settings that determine how the DNS server will function on a network and how those settings are stored and retrieved when they are needed.
The DNS server list of restricted interfaces does not contain a valid IP address for the server computer.
Correct the network interface problem
On computers with more than one network interface, the DNS server can be configured to respond to Domain Name System (DNS) requests on one or more of the interfaces. If the list of interface addresses is not correct, the DNS server is not able to respond to requests from other computers on the network.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To correct the IP addresses that the DNS server is configured to use:
1.On the DNS server, start Server Manager. To start Server Manager, click Start, click Administrative Tools, and then click Server Manager.
2.In the console tree, double-click Roles, double-click DNS Server, and then double-click DNS.
3.Right-click the DNS server, and then click Properties.
4.On the Interfaces tab, ensure that All IP addresses is selected or determine if any address in the IP addresses list is not valid for the server's network interfaces.
5.Clear the check box next to the invalid addresses, and then click OK.
6.Right-click the DNS server, click All Tasks, and then click Restart.
http://technet.microsoft.com/en-us/library/dd349562(v=ws.10).aspx
Target | Microsoft.Windows.Server.DNS.Server | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Error | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | DNS Server |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
Alert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.Windows.Server.DNS.Configuration.InvalidListenAddresses" Enabled="true" Target="Microsoft.Windows.Server.DNS.Server" ConfirmDelivery="true" Remotable="true" Priority="Normal" DiscardLevel="100">
<Category>Alert</Category>
<DataSources>
<DataSource ID="DS" TypeID="Windows!Microsoft.Windows.EventProvider">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>DNS Server</LogName>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery Type="UnsignedInteger">EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value Type="UnsignedInteger">410</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>2</Severity>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.Server.DNS.Configuration.InvalidListenAddresses.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDisplayNumber$</AlertParameter1>
<AlertParameter2>$Data/EventSourceName$</AlertParameter2>
<AlertParameter3>$Data/Channel$</AlertParameter3>
<AlertParameter4>$Data/EventDescription$</AlertParameter4>
</AlertParameters>
<Suppression>
<SuppressionValue>$Data/LoggingComputer$</SuppressionValue>
</Suppression>
<Custom1/>
<Custom2/>
<Custom3/>
<Custom4/>
<Custom5/>
<Custom6/>
<Custom7/>
<Custom8/>
<Custom9/>
<Custom10/>
</WriteAction>
</WriteActions>
</Rule>