The DNS server failed to initialize WINSR reverse lookup, through NetBIOS adapter status lookup. The server will continue to run but will not attempt to perform WINS reverse lookups. This may be due to an incorrect configuration. If WINSR lookup is not required, remove WINSR records from zone data files and reload modified zones or restart the DNS server. If the DNS server should support WINSR reverse lookup, restart the server computer and verify that the WINS/NetBT configuration for TCP/IP client properties on the computer are correctly set.
The DNS server encountered invalid token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring ...
The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions: ...
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 WINSR reverse lookup, through NetBIOS adapter status lookup. The server will continue ...
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 detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...