UI Translation

Windows Server 2003

  1. The DNS server could not parse the token "%1" in zone file %2 at line %3. Although the DNS server will continue to load, ...
  2. The DNS server could not parse the zone file %1 at line %2. Although the DNS server continues to load, ignoring this line, ...
  3. The DNS server could not parse zone file %1 for zone %2. Check that the zone file is located in the %SystemRoot%\System32\Dns ...
  4. The DNS server could not signal the service "%1". The error was %2. There may be interoperability problems between the DNS ...
  5. The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size ...
  6. The DNS server created an CNAME (alias) loop loading CNAME at %1. One link in CNAME loop: DNS name %2 is an alias for CNAME ...
  7. The DNS server created CNAME (alias) loop caching CNAME resource records (RRs). The record is ignored, since CNAME loops ...
  8. The DNS server detected that it is not enlisted in the replication scope of the directory partition %1. This prevents the ...
  9. The DNS server detected that it is not enlisted in the replication scope of the directory partition %1. This prevents the ...
  10. The DNS server did not bind to all IP addresses available on this server. Please use the DnsManger server properties interfaces ...
  11. The DNS server did not detect any zones of either primary or secondary type during initialization. It will not be authoritative ...
  12. The DNS server does not have a cache or other database entry for root name servers. Either the root hints file, cache.dns, ...
  13. The DNS server encountered a 'forwarders' directive in with no forwarding addresses in file %1 at line %2. Although the DNS ...
  14. The DNS server encountered a 'slave' directive without a preceding forwarders list in file %1 at line %2. Although the server ...
  15. The DNS server encountered a bad packet from %1. Packet processing leads beyond packet length. The event data contains the ...
  16. The DNS server encountered a CNAME (alias) resource record (RR) in zone file %1 at line %2 for a domain name with existing ...
  17. The DNS server encountered a domain name exceeding the maximum length in the packet from %1. The event data contains the ...
  18. The DNS server encountered a name outside of the specified zone in zone file %1 at line %2. Although the DNS server continues ...
  19. The DNS server encountered a name with a label whose length exceeds the maximum of 63 bytes from %1. The event data contains ...
  20. The DNS server encountered a packet addressed to itself on IP address %1. The packet is for the DNS name "%2". The packet ...
  21. The DNS server encountered a packet name exceeding the maximum label count from %1. The event data contains the DNS packet. ...
  22. The DNS server encountered a problem while attempting to load the zone. The transfer of zone data from the master server ...
  23. The DNS server encountered a problem while attempting to load the zone. The zone data may not be available in Active Directory, ...
  24. The DNS server encountered a problem while attempting to load the zone. The zone file may not be found, or the zone data ...
  25. The DNS server encountered a resource record (RR) in the zone file %1 at line %2 for a domain name with an existing CNAME ...
  26. The DNS server encountered a text string "%1" in zone file %2 at line %3 that exceeds the maximum permissible length. Although ...
  27. The DNS server encountered a token "%1" of the wrong format in zone file %2 at line %3. Although the DNS server continues ...
  28. The DNS server encountered a WINS reverse lookup (WINSR) resource record (RR) without a domain specified for resulting names ...
  29. The DNS server encountered an CNAME (alias) resource record (RR) in zone file %1 at line %2 that forms an CNAME loop with ...
  30. The DNS server encountered an error writing current configuration back to boot file. Verify that the current boot file contains ...
  31. The DNS server encountered an error writing to file. Most likely the server disk is full. Free some disk space at the server ...
  32. The DNS server encountered an invalid "@" token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  33. The DNS server encountered an invalid DNS update message from %1. The packet was rejected. The event data contains the DNS ...
  34. The DNS server encountered an invalid domain name in a packet from %1. The packet will be rejected. The event data contains ...
  35. The DNS server encountered an invalid host (A) resource record in zone file %1 at line %2. The use of A resource records ...
  36. The DNS server encountered an invalid IP address "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  37. The DNS server encountered an invalid IPv6 address "%1" in zone file %2 at line %3. Although the DNS server continues to ...
  38. The DNS server encountered an invalid name server (NS) resource record in zone file %1 at line %2. The use of NS resource ...
  39. The DNS server encountered an invalid preference value "%1" in zone file %2 at line %3. The preference must be a valid 16-bit ...
  40. The DNS server encountered an invalid response message from %1. The packet was rejected. The event data contains the DNS ...
  41. The DNS server encountered an invalid SOA (Start Of Authority) resource record (RR) in file %1 at line %2. An SOA record ...
  42. The DNS server encountered an invalid WINS reverse lookup (WINSR) resource record (RR) in file %1 at line %2. WINSR records ...
  43. The DNS server encountered an non-writeable or unknown resource record (RR) type when writing the zone database to file. ...
  44. The DNS server encountered an unknown boot option %1 in file %2 at line %3. The option is ignored. You may want to remove ...
  45. The DNS server encountered an unknown or unsupported resource record (RR) type %1 in zone file %2 at line %3. Although the ...
  46. The DNS server encountered an unknown protocol writing a well known service (WKS) resource record to the zone file. The event ...
  47. The DNS server encountered an unknown service port writing a well known service (WKS) resource record to the zone file. The ...
  48. The DNS server encountered an unknown WINS-to-DNS mapping flag %1 in file %2 at line %3. Although the DNS server continues ...
  49. The DNS server encountered an unsupported 'directory' directive in the server boot file %1 at line %2. All database files ...
  50. The DNS server encountered domain name "%1" exceeding maximum length. Although the DNS server continues to load, ignoring ...
  51. The DNS server encountered invalid class token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  52. The DNS server encountered invalid domain name "%1" in zone file %2 at line %3. Although the DNS server continues to load, ...
  53. The DNS server encountered invalid or corrupted forwarder parameters in registry data. To fix the forwarders: - connect to ...
  54. The DNS server encountered invalid token "%1" in zone file %2 at line %3. Although the DNS server continues to load, ignoring ...
  55. The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions: ...
  56. The DNS server encountered the directive '%1' in file %2 at line %3. The directive is not yet supported and was ignored. ...
  57. The DNS server encountered the port "%1" specified for the well known service (WKS) resource record (RR) in zone file %2 ...
  58. The DNS server failed to initialize WINSR reverse lookup, through NetBIOS adapter status lookup. The server will continue ...
  59. The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been ...
  60. The DNS server has completed a scavenging cycle but no nodes were visited. Possible causes of this condition include: 1) ...
  61. The DNS server has completed a scavenging cycle: Visited Zones = %1, Visited Nodes = %2, Scavenged Nodes = %3, Scavenged ...
  62. The DNS server has detected that for the primary zone %1 its has no zone file name stored in registry data. You can either ...
  63. The DNS server has detected that the secondary zone %1 has no master IP addresses in registry data. Secondary zones require ...
  64. The DNS server has detected that the zone %1 has a missing or corrupted zone type in registry data. To correct the problem, ...
  65. The DNS server has detected that the zone %1 has invalid or corrupted registry data. To correct the problem, you can delete ...
  66. The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning ...
  67. The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine ...
  68. The DNS server has encountered numerous run-time events. To determine the initial cause of these run-time events, examine ...
  69. The DNS server has invalid or corrupted registry parameter %1. To correct the problem, you can delete the applicable registry ...
  70. The DNS server has moved the AD-integrated root hint data for all DNS servers in this domain to the %1 directory partition. ...
  71. The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were ...
  72. The DNS server is bound to a large number of IP addresses. Each of these server IP addresses consumes additional system resources ...
  73. The DNS server is configured to forward to a non-recursive DNS server at %1. DNS servers in forwarders list MUST be configured ...
  74. The DNS server is ignoring an invalid resource record in zone file %1 at line %2. See the previously logged event for a description ...
  75. The DNS server is not root authoritative and no root hints were specified in the cache.dns file. Where the server is not ...
日本語
Japanese English
English (United States)