The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) No zones are configured for scavenging by this server. 2) A scavenging cycle was performed within the last %1 minutes. 3) An error occurred during scavenging. The next scavenging cycle is scheduled to run in %2 hours. The event data will contain the error code if there was an error during the scavenging cycle.
The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored. ...
The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
The DNS server has completed a scavenging cycle: Visited Zones = %1, Visited Nodes = %2, Scavenged Nodes = %3, Scavenged ...
The DNS server has completed background loading of zone %1. The zone is now available for updates and zone transfers if allowed ...
The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...