Windows 7

  1. The DNS server encountered a text string "%1" in zone file %2 at line %3 that exceeds the maximum permissible length. Although ...
  2. The DNS server encountered a token "%1" of the wrong format in zone file %2 at line %3. Although the DNS server continues ...
  3. The DNS server encountered a WINS reverse lookup (WINSR) resource record (RR) without a domain specified for resulting names ...
  4. The DNS server encountered an alias (CNAME or DNAME) resource record (RR) in zone file %1 at line %2 that forms an alias ...
  5. The DNS server encountered an error writing current configuration back to boot file. Verify that the current boot file contains ...
  6. The DNS server encountered an error writing to file. Most likely the server disk is full. Free some disk space at the server ...
  7. The DNS server encountered an invalid "@" token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  8. The DNS server encountered an invalid DNS update message from %1. The packet was rejected. The event data contains the DNS ...
  9. The DNS server encountered an invalid domain name in a packet from %1. The packet will be rejected. The event data contains ...
  10. The DNS server encountered an invalid host (A) resource record in zone file %1 at line %2. The use of A resource records ...
  11. The DNS server encountered an invalid IP address "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  12. The DNS server encountered an invalid IPv6 address "%1" in zone file %2 at line %3. Although the DNS server continues to ...
  13. The DNS server encountered an invalid name server (NS) resource record in zone file %1 at line %2. The use of NS resource ...
  14. The DNS server encountered an invalid preference value "%1" in zone file %2 at line %3. The preference must be a valid 16-bit ...
  15. The DNS server encountered an invalid response message from %1. The packet was rejected. The event data contains the DNS ...
  16. The DNS server encountered an invalid SOA (Start Of Authority) resource record (RR) in file %1 at line %2. An SOA record ...
  17. The DNS server encountered an invalid WINS reverse lookup (WINSR) resource record (RR) in file %1 at line %2. WINSR records ...
  18. The DNS server encountered an non-writeable or unknown resource record (RR) type when writing the zone database to file. ...
  19. The DNS server encountered an unknown boot option %1 in file %2 at line %3. The option is ignored. You may want to remove ...
  20. The DNS server encountered an unknown or unsupported resource record (RR) type %1 in zone file %2 at line %3. Although the ...
  21. The DNS server encountered an unknown protocol writing a well known service (WKS) resource record to the zone file. The event ...
  22. The DNS server encountered an unknown WINS-to-DNS mapping flag %1 in file %2 at line %3. Although the DNS server continues ...
  23. The DNS server encountered an unsupported 'directory' directive in the server boot file %1 at line %2. All database files ...
  24. The DNS server encountered domain name "%1" exceeding maximum length. Although the DNS server continues to load, ignoring ...
  25. The DNS server encountered error %1 attempting to load zone %2 from Active Directory. The DNS server will attempt to load ...
  26. The DNS server encountered error %1 building the zone list from Active Directory. The DNS server will sleep for %2 seconds ...
  27. The DNS server encountered invalid class token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  28. The DNS server encountered invalid domain name "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  29. The DNS server encountered invalid or corrupted forwarder parameters in registry data. To fix the forwarders: - connect to ...
  30. The DNS server encountered invalid token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring ...
  31. The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions: ...
  32. The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored. ...
  33. The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
  34. The DNS server failed to initialize NetBIOS lookups to support WINSR for reverse lookup zones. The server will continue to ...
  35. The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
  36. The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
  37. The DNS server has completed a scavenging cycle: Visited Zones = %1, Visited Nodes = %2, Scavenged Nodes = %3, Scavenged ...
  38. The DNS server has completed background loading of zone %1. The zone is now available for updates and zone transfers if allowed ...
  39. The DNS server has deleted all records for a corrupt DNS node from Active Directory. The DNS node's distinguished name was ...
  40. The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...
  41. The DNS server has detected that the application directory partition %1 has finished replicating onto this domain controller. ...
  42. The DNS server has detected that the application directory partition %1 is replicating onto this domain controller. DNS data ...
  43. The DNS server has detected that the secondary zone %1 has no master IP addresses in registry data. Secondary zones require ...
  44. The DNS server has detected that the zone %1 has a missing or corrupted zone type in registry data. To correct the problem, ...
  45. The DNS server has detected that the zone %1 has invalid or corrupted registry data. To correct the problem, you can delete ...
  46. The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning ...
  47. The DNS server has finished the background loading of zones. All zones are now available for DNS updates and zone transfers, ...
  48. The DNS server has invalid or corrupted registry parameter %1. To correct the problem, you can delete the applicable registry ...
  49. The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the %1 directory partition. ...
  50. The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were ...
  51. The DNS server is being contacted to retrieve the zone information. Depending upon the load on the DNS Server, there may ...
  52. The DNS server is experiencing high SOA query load. This may be caused by a large number of local client machines performing ...
  53. The DNS server is ignoring an invalid resource record in zone file %1 at line %2. See the previously logged event for a description ...
  54. The DNS server is not root authoritative and no root hints were specified in the cache.dns file. Where the server is not ...
  55. The DNS server is now booting from the registry or directory. The existing server boot file will no longer be read by the ...
  56. The DNS server is now starting to load zone %1 in the background. While the zone is being loaded all DNS updates and zone ...
  57. The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the ...
  58. The DNS server list is empty. The local IP address will be configured as the primary DNS server address because Microsoft ...
  59. The DNS server list of restricted interfaces contains IP addresses that are not configured for use at the server computer. ...
  60. The DNS server list of restricted interfaces does not contain a valid IP address for the server computer. The DNS server ...
  61. The DNS server received a bad DNS query from %1. The query was rejected or ignored. The event data contains the DNS packet. ...
  62. The DNS server received a bad TCP-based DNS message from %1. The packet was rejected or ignored. The event data contains ...
  63. The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full ...
  64. The DNS server received indication that zone %1 was deleted from the Active Directory. Since this zone was an Active Directory ...
  65. The DNS server refused to transfer the zone %1 to your computer. If this is incorrect, check the zone transfer security settings ...
  66. The DNS server role is being installed on a domain controller, and so DNS zones will be integrated with Active Directory ...
  67. The DNS Server service stores and resolves DNS names of clients in order to enable computers to locate other computers and ...
  68. The DNS server timed out attempting an Active Directory service operation on %1. Check Active Directory to see that it is ...
  69. The DNS server timed out attempting to write resource records to the Active Directory at %1. Check that the directory is ...
  70. The DNS server unable to write zone file %1 for zone %2. Most likely the server disk is full. Free some disk space and re-initiate ...
  71. The DNS server unexpected end of line, in zone file %1 at line %2. To correct the problem, fix this line in the zone file, ...
  72. The DNS server was unable to add or write an update of domain name %1 in zone %2 to the Active Directory. Check that the ...
  73. The DNS server was unable to add zone %1 to the Active Directory. Check that the Active Directory is available. Note that ...
  74. The DNS server was unable to begin background loading of Active Directory-integrated zones. There may be a system resource ...
  75. The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information ...