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.
A zone expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone.
Correct master server problems
The master-server configuration for a secondary zone is not correct, which is preventing the zone from being transferred from the master server.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To correct problems with zone transfers from a master server:
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.Expand the DNS server, and then expand the folder that contains the affected zone.
4.Right-click the zone, and then click Properties.
5.On the General tab, confirm that the list contains the correct IP addresses and fully qualified domain names (FQDNs) of the master servers of the zone.
If the list is correct, ensure that the listed master servers are functioning properly. Ensure that zone transfers are allowed on the master server and that, if zone transfers are restricted by IP address, this server is included in the list. If not, correct the problem, and then restart the zone transfer.
To confirm that the local server is included in the list of servers that can receive zone transfers:
1.On the DNS server, start DNS Manager. To start DNS Manager, on a DNS server, click Start, click Administrative Tools, and then click DNS.
2.Connect to the master server. To connect to a DNS server, right-click DNS, click Connect to DNS Server, click The following computer, type the DNS name or IP address of the remote DNS server, and then click OK.
3.Expand the server, and then expand the folder that contains the zone.
4.Right-click the zone, click Properties, and then click Zone Transfers.
5.If it is not already selected, click Allow zone transfers.
6.Do one of the following:
If Only to servers listed on the Name Servers tab is selected, click Name Servers, and confirm that the server that hosts the secondary zone is listed with the correct IP address in the Name servers list.
If Only to the following servers is selected, confirm that the server that hosts the secondary zone is listed with the correct IP address in the list.
To restart a zone transfer:
1.In Server Manager or DNS Manager, expand DNS, expand the server that hosts the secondary zone, and then expand the folder that contains the zone.
2.Right-click the zone, and then click Reload from master.
http://technet.microsoft.com/en-us/library/dd349563(v=ws.10).aspx
Target | Microsoft.Windows.DNSServer.2016.Server | ||
Category | Alert | ||
Enabled | True | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
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.DNSServer.2016.Configuration.ZoneExpiration" Enabled="true" Target="Microsoft.Windows.DNSServer.2016.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">6527</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="Alert" TypeID="Health!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertName/>
<AlertDescription/>
<AlertOwner/>
<AlertMessageId>$MPElement[Name="Microsoft.Windows.DNSServer.2016.Configuration.ZoneExpiration.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>