Behind the scene, that rule uses the following powershell code to collect QueriesReceived counter :
$allStatistics = Get-DnsServerStatistics -ZoneName $zone.ZoneName -ComputerName $PrincipalName -ErrorAction Stop
[double]$QueriesReceived = 0
[double]$QueriesFailure = 0
[double]$QueriesNameError = 0
$zoneQueryStatistics = @()
$zoneQueryStatistics += $allStatistics.ZoneQueryStatistics
if ($zoneQueryStatistics -ne $null -and $zoneQueryStatistics.Count -gt 0)
{
foreach ($zoneQueryStat in $zoneQueryStatistics)
{
$QueriesReceived += $zoneQueryStat.QueriesReceived
$QueriesNameError += $zoneQueryStat.QueriesNameError
$QueriesFailure += $zoneQueryStat.QueriesFailure
}
}
$bag = $momAPI.CreatePropertyBag()
$bag.AddValue("ServerName", $PrincipalName)
$bag.AddValue("ZoneName", $zone.ZoneName)
$bag.AddValue("QueriesReceived", $QueriesReceived)
$bag.AddValue("QueriesNameError", $QueriesNameError)
$bag.AddValue("QueriesFailure", $QueriesFailure)
$bag
And the documentation for Get-DnsServerStatistics cmdlet does indeed show that it returns the number of QueriesReceived "since last cleared statistics", which basically is last server restart unless someone manually cleared those statistics.
I would consider that counter rather useless in its current form, it would be more interesting if it had been authored using a Delta performance data provider (which would return the increase since last measurement instead of the raw value)