Microsoft KB Archive/842006

= DNS event messages 1616 through 6702 in Windows Server 2003 =

Article ID: 842006

Article Last Modified on 10/30/2006

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)

-





INTRODUCTION
This article describes DNS server events that may be displayed in the event logs on a Microsoft Windows Server 2003-based DNS server. This article describes event ID 1616 through event ID 6702.

For events with lower number sequences, view the following article in the Microsoft Knowledge Base:

884114 DNS event messages 1 through 1614 in Windows Server 2003

Note There is no event 1615.



1616
MessageId=1616

Severity=Error

SymbolicName=DNS_EVENT_TEXT_STRING_TOO_LONG

The DNS server encountered a text string &quot;%1&quot; in zone file %2 at line %3 that exceeds the maximum permissible length. Although the DNS server continues to load, ignoring this resource record (RR), it is strongly recommended that you either correct this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1617
MessageId=1617

Severity=Error

SymbolicName=DNS_EVENT_INVALID_IP_ADDRESS_STRING

The DNS server encountered an invalid IP address &quot;%1&quot; in zone file %2 at line %3. Although the DNS server continues to load, ignoring this resource record (RR), it is recommended that you either correct this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1618
MessageId=1618

Severity=Error

SymbolicName=DNS_EVENT_INVALID_IPV6_ADDRESS

The DNS server encountered an invalid IPv6 address &quot;%1&quot; in zone file %2 at line %3. Although the DNS server continues to load, ignoring this resource record (RR), it is recommended that you either correct this RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1619
MessageId=1619

Severity=Error

SymbolicName=DNS_EVENT_UNKNOWN_PROTOCOL

The DNS server could not find protocol &quot;%1&quot; specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1620
MessageId=1620

Severity=Error

SymbolicName=DNS_EVENT_UNKNOWN_SERVICE

The DNS server could not find the service &quot;%1&quot; specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. Although the DNS server continues to load, ignoring this RR, it is recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1621
MessageId=1621

Severity=Error

SymbolicName=DNS_EVENT_WKS_PORT_UNSUPPORTED

The DNS server encountered the port &quot;%1&quot; specified for the well known service (WKS) resource record (RR) in zone file %2 at line %3. This port exceeds the maximum port supported for the WKS RR. Although the DNS server continues to load, ignoring this RR, it is strongly recommended that you either correct this WKS RR or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1650
Messageid=1650

Severity=Error

SymbolicName=DNS_EVENT_INVALID_WINS_RECORD

The DNS server encountered invalid WINS record in file %1, line %2. WINS records are subject to the following conditions:


 * 1) WINS records must be in forward lookup zone (not in in-addr.arpa domain).
 * 2) Only one WINS record may be specified in a zone file.
 * 3) WINS records must belong to the zone root (the WINS record name must be the origin of the zone). If WINS lookup is desired for names in a sub-domain of the zone, then the sub-domain must be split into its own zone.
 * 4) WINS records must specify at least one WINS server.

The format of a WINS record:

WINS [LOCAL] [L] [C] [WINS IPs...]

Examples (zone root assumed to be current origin):

WINS LOCAL L1 C10 10.10.10.1 10.10.10.2 10.10.10.3

WINS 10.10.10.1

For more information, see &quot;Using WINS lookup&quot; in the online Help.

1651
Messageid=1651

Severity=Error

SymbolicName=DNS_EVENT_INVALID_NBSTAT_RECORD

The DNS server encountered an invalid WINS reverse lookup (WINSR) resource record (RR) in file %1 at line %2.

WINSR records are subject to the following conditions:


 * 1) WINSR record must be in reverse lookup zone (under in-addr.arpa domain).
 * 2) Only one WINSR record may be specified in a zone file.
 * 3) WINSR record must belong to the zone root (the WINS record name must be the origin of the zone).
 * 4) WINSR record must specify a domain for the resulting name.

The format of a WINSR record:

WINSR [LOCAL] [L] [C]

Examples (zone root assumed to be current origin):

WINSR LOCAL L1 C10 microsoft.com.

WINSR wins.microsoft.com.

For more information, see &quot;Using WINS lookup&quot; in the online Help.

1654
MessageId=1654

Severity=Error

SymbolicName=DNS_EVENT_UNKNOWN_WINS_FLAG

The DNS server encountered an unknown WINS-to-DNS mapping flag %1 in file %2 at line %3. Although the DNS server continues to load, ignoring this flag, it is recommended that you either correct the associated resource record or remove it from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

1656
MessageId=1656

Severity=Error

SymbolicName=DNS_EVENT_NO_NBSTAT_DOMAIN

The DNS server encountered a WINS reverse lookup (WINSR) resource record (RR) without a domain specified for resulting names in zone file %1 at line %2. This field is required for mapping names that are found in WINS reverse lookup to fully-qualified DNS domain names. It is appended to the NetBIOS computer names resolved by NetBIOS adapter status queries. Although the DNS server will continue to load, ignoring this RR, it is recommended that you either correct the WINSR RR or disable WINS reverse lookup and/or remove the RR from the zone file. The zone file is located in the %SystemRoot%\System32\Dns directory.

For more information, see &quot;Using WINS lookup&quot; in the online Help.

2001
MessageId=2001

Severity=Success

SymbolicName=DNS_BOOTFILE_BACKUP_MESSAGE

The DNS server is now booting from the registry or directory. The existing server boot file will no longer be read by the DNS server at startup. For any new zones that you add or for changes you make to zone information, you must make them using the DNS console. The previous DNS server boot file has been moved to the %SystemRoot%\System32\Dns\backup directory. To return to using a boot file, use the DNS console and reconfigure the boot method for the server. For more information, see &quot;To change the boot method used by the DNS server&quot; in the online Help.

2002
MessageId=2002

Severity=Informational

SymbolicName=DNS_EVENT_BOOTFILE_REWRITE

The DNS server has written a new version of the boot file. Either new zones or changes to existing zone information were made through the DNS console that required the DNS Server to update the information in this file. A copy of the previous boot file has been moved to the %SystemRoot%\System32\Dns\backup directory.

2003
MessageId=2003

Severity=Error

SymbolicName=DNS_EVENT_BOOTFILE_WRITE_ERROR

The DNS server encountered an error writing current configuration back to boot file. Verify that the current boot file contains all of the desired information. The Boot file is located in the %SystemRoot%\System32\Dns directory.

2005
MessageId=2005

Severity=Informational

SymbolicName=DNS_EVENT_SWITCH_TO_BOOTFILE

The DNS server has been reconfigured to boot from a boot file. Current server and zone configuration information has been written to this file. To return to booting from the registry or Active Directory, use the DNS console and reconfigure the boot method for the server. For more information, see &quot;To change the boot method used by the DNS server&quot; in the online Help.

2200
Messageid=2200

Severity=Error

SymbolicName=DNS_EVENT_REGISTRY_OPEN_FAILED

The DNS server could not open a registry key. Reinstall the DNS server if it was not able to be started. If the DNS server started, but couldn't load a zone, reload the zone or restart the DNS server.

2202
Messageid=2202

Severity=Error

SymbolicName=DNS_EVENT_REGISTRY_WRITE_FAILED

The DNS server could not write a registry key. The server disk could be full or corrupted or the maximum permissible size for the server registry has been reached. The DNS server will not be able to save server or zone configuration parameters to in the registry unless the problem is fixed.

2203
Messageid=2203

Severity=Error

SymbolicName=DNS_EVENT_REGISTRY_DELETE_FAILED

The DNS server could not delete a registry key. The registry is likely corrupted. The DNS server will not be able to save DNS server or zone configuration parameters in the registry unless the problem is fixed.

2204
Messageid=2204

Severity=Error

SymbolicName= DNS_EVENT_INVALID_REGISTRY_VALUE

The registry value HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters\%1 contains an invalid value or could not be read. The DNS server cannot start. You must change this value to valid data or delete it and then attempt to restart the DNS service.

2501
Messageid=2501

Severity=Informational

SymbolicName=DNS_EVENT_AGING_SCAVENGING_END

DNS service has completed a scavenging cycle: Visited Nodes = %1, Scavenged Nodes = %2, Scavenged Records = %3. This cycle took %4 seconds. Next cycle is scheduled in %5 hours. The record data may contain error code.

2502
Messageid=2502

Severity=Informational

SymbolicName = DNS_EVENT_AGING_SCAVENGING_END_NO_WORK

The DNS server has completed a scavenging cycle but no nodes were visited. The 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.

2600
Messageid=2600

Severity=Informational

SymbolicName = DNS_EVENT_SERVER_SUPPRESSION

To prevent the event log from filling up too rapidly the DNS server has suppressed event ID %1 a total of %2 times in the last %3 minutes.

2601
Messageid=2601

Severity=Informational

SymbolicName = DNS_EVENT_ZONE_SUPPRESSION

To prevent the event log from filling up too rapidly the DNS server has suppressed event ID %1 a total of %2 times in the last %3 minutes. These events were in relation to zone %4.

2630
Messageid=2630

Severity=Informational

SymbolicName = DNS_EVENT_AUTOCONFIG_FAILED

The DNS server could not configure the network connections of this computer with the local computer's IP address as the preferred DNS server, because this computer is connected to networks with different or invalid DNS namespaces. Manual configuration of the local DNS server to perform name resolution on one or more of the namespaces is required before the preferred DNS servers of this computer should be modified. If the network connections of this computer are not configured with the local computer's IP address as the preferred DNS server, this computer may not be able to dynamically register DC locator records in DNS. Absence of these records may prevent other Active Directory domain controllers and domain members from locating this domain controller.

User Action: Ensure that DC locator DNS records enumerated in the file %SystemRoot%\system32\config\netlogon.dns are registered on the local DNS server. If these records are not registered in DNS, follow one of these steps:


 * Add a delegation to this DNS server to the parent DNS zone that matches the name of the Active Directory domain.
 * Configure the local DNS server with appropriate root hints and forwarders, if necessary, and configure the network connections of this computer with the local computer's IP address as the preferred DNS server.

Note Other computers using other DNS servers as their preferred or alternate DNS servers may not be able to locate this domain controller, unless the DNS infrastructure is properly configured.

2631
Messageid=2631

Severity=Informational

SymbolicName = DNS_EVENT_AUTOCONFIG_SUCCEEDED

The DNS server successfully autoconfigured: %1 %2 %3

3000
MessageId=3000

Severity=Warning

SymbolicName=DNS_EVENT_START_LOG_SUPPRESS

The DNS server is logging numerous run-time events. For information about these events, see previous DNS Server event log entries. To prevent the DNS Server from clogging server logs, further logging of this event and other events with higher Event IDs will now be suppressed.

3150
MessageId=3150

Severity=Informational

SymbolicName=DNS_EVENT_ZONE_WRITE_COMPLETED

The DNS server wrote version %1 of zone %2 to file %3.

3151
MessageId=3151

Severity=Error

SymbolicName=DNS_EVENT_ZONE_WRITE_FAILED

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 zone write.

3152
MessageId=3152

Severity=Error

SymbolicName=DNS_EVENT_FILE_NOT_OPENED_FOR_WRITE

The DNS server was unable to open file %1 for write. Most likely the file is a zone file that is already open. Close the zone file and re-initiate zone write.

3153
MessageId=3153

Severity=Error

SymbolicName=DNS_EVENT_WRITE_FILE_FAILURE

The DNS server encountered an error writing to file. Most likely the server disk is full. Free some disk space at the server and re-initiate zone write. The event data is the error code.

3160
MessageId=3160

Severity=Error

SymbolicName=DNS_EVENT_UNWRITABLE_RECORD_TYPE

The DNS server encountered a non-writable or unknown resource record (RR) type when writing the zone database to file. The event data is applicable RR type.

3162
MessageId=3162

Severity=Error

SymbolicName=DNS_EVENT_UNKNOWN_PROTOCOL_NUMBER

The DNS server encountered an unknown protocol writing a well known service (WKS) resource record to the zone file. The event data is applicable the protocol number.

3163
MessageId=3163

Severity=Error

SymbolicName=DNS_EVENT_UNKNOWN_SERVICE_PORT

The DNS server encountered an unknown service port writing a well known service (WKS) resource record to the zone file. The event data is applicable the port.

4000
MessageId=4000

Severity=Error

SymbolicName=DNS_EVENT_DS_OPEN_FAILED

The DNS server was unable to open Active Directory. This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.

4001
MessageId=4001

Severity=Error

SymbolicName=DNS_EVENT_DS_ZONE_OPEN_FAILED

The DNS server was unable to open zone %1 in the Active Directory. This DNS Server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and reload the zone. The event data is the error code.

4002
MessageId=4002

Severity=Error

SymbolicName=DNS_EVENT_DS_ZONE_ADD_FAILED

The DNS server was unable to add zone %1 to the Active Directory. Check that the Active Directory is available. Note that the zone will not be added to and written to the directory unless you re-attempt adding the zone using the DNS console. The event data contains the error. For more information see &quot;Add and Remove Zones&quot; in the online Help.

4003
MessageId=4003

Severity=Error

SymbolicName=DNS_EVENT_DS_ZONE_DELETE_FAILED

The DNS server was unable to delete zone %1 in the Active Directory. Check that the Active Directory is functioning properly. Note that this zone will not be removed from the directory unless you retry deleting of the zone using the DNS console. The event data contains the error. For more information see &quot;Add and Remove Zones&quot; in the online Help.

4004
MessageId=4004

Severity=Error

SymbolicName=DNS_EVENT_DS_ZONE_ENUM_FAILED

The DNS server was unable to complete directory service enumeration of zone %1. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The event data contains the error.

4005
MessageId=4005

Severity=Informational

SymbolicName=DNS_EVENT_DS_ZONE_DELETE_DETECTED

The DNS server received indication that zone %1 was deleted from Active Directory. Since this zone was an Active Directory zone, it has been deleted from the DNS server.

4006
MessageId=4006

Severity=Error

SymbolicName=DNS_EVENT_DS_NODE_LOAD_FAILED

The DNS server was unable to create a name in memory for name %1 in zone %2 in the Active Directory. This directory name is ignored. Use the DNS console to re-create the records associated with this name or check that the Active Directory is functioning properly and reload the zone. The event data contains the error.

4010
MessageId=4010

Severity=Error

SymbolicName=DNS_EVENT_DS_RECORD_LOAD_FAILED

The DNS server was unable to load a resource record (RR) from the directory at %1 in zone %2. Use the DNS console to recreate this RR or check that the Active Directory is functioning properly and reload the zone. The event data contains the error.

4011
MessageId=4011

Severity=Error

SymbolicName=DNS_EVENT_DS_WRITE_FAILED

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 Active Directory is functioning properly and add or update this domain name using the DNS console. The event data contains the error.

4012
MessageId=4012

Severity=Error

SymbolicName=DNS_EVENT_DS_WRITE_TIMEOUT

The DNS server timed out attempting to write resource records to the Active Directory at %1. Check that the directory is functioning properly and add or update the records using the DNS console. The event data contains the error.

4013
MessageId=4013

Severity=Warning

SymbolicName=DNS_EVENT_DS_OPEN_WAIT

The DNS server was unable to open the Active Directory. This DNS server is configured to use directory service information and cannot operate without access to the directory. The DNS server will wait for the directory to start. If the DNS server is started but the appropriate event has not been logged, then the DNS server is still waiting for the directory to start.

4014
MessageId=4014 Severity=Error SymbolicName=DNS_EVENT_DS_SECURITY_INIT_FAILURE

The DNS server was unable to initialize Active Directory security interfaces. Check that the Active Directory is functioning properly and restart the DNS server. The event data contains the error.

4015
MessageId=4015

Severity=Error

SymbolicName=DNS_EVENT_DS_INTERFACE_ERROR

The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The event data contains the error.

4016
MessageId=4016

Severity=Error

SymbolicName=DNS_EVENT_DS_LDAP_TIMEOUT

The DNS server timed out attempting an Active Directory service operation on %1. Check Active Directory to see that it is functioning properly. The event data contains the error.

5105
MessageId=5105

Severity=Error

SymbolicName=DNS_EVENT_ADDING_RR_AT_CNAME

The DNS server attempted to cache an CNAME (alias) resource record for the domain node. The operation failed, since the CNAME RR must be the only RR for its domain name.

5106
MessageId=5106

Severity=Error

SymbolicName=DNS_EVENT_CNAME_NOT_ALONE

The DNS server attempted to cache an CNAME (alias) resource record (RR) for a domain name with existing RRs. The CNAME RR is ignored, since it must be the only RR for its domain name.

5107
MessageId=5107

Severity=Error

SymbolicName=DNS_EVENT_CNAME_LOOP

The DNS server created CNAME (alias) loop caching CNAME resource records (RRs). The record is ignored, since CNAME loops are not allowed.

5108
MessageId=5108

Severity=Error

SymbolicName=DNS_EVENT_CNAME_LOOP_LINK

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 %3. See adjoining messages for other links in the CNAME loop.

5500
MessageId=5500

Severity=Warning

SymbolicName=DNS_EVENT_BAD_QUERY

The DNS server received a bad DNS query. The query was rejected or ignored.

5501
Messageid=5501

Severity=Warning

SymbolicName=DNS_EVENT_BAD_PACKET_LENGTH

The DNS server encountered a bad packet from %1. Packet processing leads beyond packet length.

5502
MessageId=5502

Severity=Warning

SymbolicName=DNS_EVENT_BAD_TCP_MESSAGE

The DNS server received a bad TCP-based DNS message from %1. The packet was rejected or ignored.

5504
Messageid=5504

Severity=Warning

SymbolicName=DNS_EVENT_INVALID_PACKET_DOMAIN_NAME

The DNS server encountered an invalid domain name in a packet from %1. The packet is rejected.

5505
Messageid=5505

Severity=Warning

SymbolicName=DNS_EVENT_PACKET_NAME_TOO_LONG

The DNS server encountered a domain name exceeding the maximum length in the packet.

5506
Messageid=5506

Severity=Warning

SymbolicName=DNS_EVENT_PACKET_NAME_BAD_OFFSET

The DNS server encountered an invalid domain name offset in a packet. The offset is the error.

5507
Messageid=5507

Severity=Warning

SymbolicName=DNS_EVENT_PACKET_NAME_OFFSET_TOO_LONG

The DNS server encountered a name offset exceeding the packet length. The offset is the error.

5508
Messageid=5508

Severity=Warning

SymbolicName=DNS_EVENT_PACKET_NAME_TOO_MANY_LABELS

The DNS server encountered a packet name exceeding the maximum label count.

5509
Messageid=5509

Severity=Warning

SymbolicName=DNS_EVENT_BAD_UPDATE_PACKET

The DNS server encountered an invalid DNS update message from %1. The packet was rejected.

5510
Messageid=5510

Severity=Warning

SymbolicName=DNS_EVENT_BAD_RESPONSE_PACKET

The DNS server encountered an invalid response message from %1. The packet was rejected.

6001
Messageid=6001

Severity=Informational

SymbolicName=DNS_EVENT_ZONEXFR_SUCCESSFUL

The DNS server successfully completed transfer of zone %1 to DNS server at %2.

6002
Messageid=6002

Severity=Informational

SymbolicName=DNS_EVENT_ZONEXFR_ABORTED

The transfer of zone %1 by the DNS Server was aborted by the server at %2. To restart the transfer of the zone, you must initiate transfer at the secondary server. Fore more information, see &quot;Initiate a zone transfer at a secondary server&quot; in the online Help.

6003
Messageid=6003

Severity=Warning

SymbolicName=DNS_EVENT_UDP_ZONE_TRANSFER

The DNS server received a request from %1 for a UDP-based transfer of the entire zone. The request was ignored because full zone transfers must be made using TCP.

6004
MessageId=6004

Severity=Warning

SymbolicName=DNS_EVENT_BAD_ZONE_TRANSFER_REQUEST

The DNS server received a zone transfer request from %1 for a non-existent or non-authoritative zone %2.

6520
MessageId=6520

Severity=Informational

SymbolicName=DNS_EVENT_ZONE_UPDATE

Zone %1 was updated to version %2 of the zone as provided from the master server at %3.

6521
MessageId=6521

Severity=Informational

SymbolicName=DNS_EVENT_ZONE_IN_SYNC

Zone %1 is synchronization with version %2 of the zone as provided from the master server at %3.

6522
MessageId=6522

Severity=Informational

SymbolicName=DNS_EVENT_ZONE_TRANSFER_IN_PROGRESS

A more recent version, version %1 of zone %2 was found at DNS server at %3. Zone transfer is in progress.

6523
MessageId=6523

Severity=Warning

SymbolicName=DNS_EVENT_XFR_MASTER_UNAVAILABLE

Zone %1 failed zone refresh check. Unable to connect to master DNS server at %2 to receive zone transfer. Check that the zone contains correct IP address for the master server or if network failure has occurred. For more information, see &quot;To update the master server for a secondary zone&quot; in the online Help. If available, you can specify more than one master server in the list for this zone.

6524
MessageId=6524

Severity=Error

SymbolicName=DNS_EVENT_AXFR_BAD_RESPONSE

Invalid response from master DNS server at %2 during attempted zone transfer of zone %1. Check The DNS server at %2 and insure that it is authoritative for this zone. This can be done by viewing or updating the list of authoritative servers for the zone. When using the DNS console, select zone %1 Properties at server %2 and click the Name Servers tab. If needed, you can add or update this server in the list there. As an alternative solution, you could also modify settings in the Zone Transfer tab to allow transfer of the zone to this and other DNS servers.

6525
MessageId=6525

Severity=Error

SymbolicName=DNS_EVENT_AXFR_REFUSED

Zone transfer request for secondary zone %1 refused by master server at %2. Check the zone at the master server %2 to verify that zone transfer is enabled to this server. To do so, use the DNS console, and select master server %2 as the applicable server, then in secondary zone %1 Properties, view the settings on the Zone Transfers tab. Based on the settings you choose, make any configuration adjustments there (or possibly in the Name Servers tab) so that a zone transfer can be made to this server.

6526
MessageId=6526

Severity=Warning

SymbolicName=DNS_EVENT_ZONE_NEWER_THAN_SERVER_VERSION

Zone %1 version %2 is newer than version %3 on DNS server at %4. The zone was not updated. DNS servers supplying zones for transfer must have the most recent version of the zone, based on the primary zone. If zone on remote server %4, is in fact the most recent version of the zone, do the following at that server:


 * 1) Stop the DNS server.
 * 2) Delete the zone file (not the zone itself).
 * 3) Restart the DNS server.

The DNS server will transfer the new version and write its zone file. When deleting the zone file at server %4, locate the file named %1.dns in the %SystemRoot%\System32\Dns directory and delete it. An alternative solution is to delete and recreate the secondary zone at server %4. This could be preferred if this server hosts large zones and restarting it at this time would be a consuming or costly operation.

6527
MessageId=6527

Severity=Error

SymbolicName=DNS_EVENT_ZONE_EXPIRATION

Zone %1 expired before it could obtain a successful zone transfer or update from a master server acting as its source for the zone. The zone has been shut down.

6530
MessageId=6530

Severity=Error

SymbolicName=DNS_EVENT_XFR_ADD_RR_AT_CNAME

During transfer of zone %1 from master at %2, the DNS Server received a resource record (RR) for domain node %3 at which an CNAME (alias) RR was already received. When used, the CNAME RR must be the only record for its domain name. The CNAME RR for %3 will be ignored.

6531
MessageId=6531

Severity=Error

SymbolicName=DNS_EVENT_XFR_CNAME_NOT_ALONE

During transfer of zone %1 from master at %2, the DNS Server received a CNAME (alias) resource record (RR) for domain node %3 for which other records of that name were already received. When used, the CNAME RR must be the only record for its domain name. The CNAME RR for %3 will be ignored.

6532
MessageId=6532

Severity=Error

SymbolicName=DNS_EVENT_XFR_CNAME_LOOP

During transfer of zone %1 from master at %2, the DNS Server received a CNAME (alias) resource record (RR) for domain node %3 which would form an CNAME loop if accepted and used. The CNAME RR for %3 is being ignored.

6533
MessageId=6533

Severity=Error

SymbolicName=DNS_EVENT_AXFR_INIT_FAILED

The DNS server could not create a zone transfer thread. The system may be out of resources. Close any applications not in use or reboot the computer to free memory. The event data contains the error.

6534
MessageId=6534

Severity=Error

SymbolicName=DNS_EVENT_XFR_ABORTED_BY_MASTER

Failed transfer of zone %1 from DNS server at %2. The DNS server at %2 aborted or failed to complete transfer of the zone. Check the DNS server at %2 and insure it is properly functioning and authoritative for zone %1.

6535
MessageId=6535

Severity=Warning

SymbolicName=DNS_EVENT_IXFR_UNSUPPORTED

The master DNS server at %2 responded to IXFR (Incremental Zone Transfer) request for zone %1 with an invalid (FORMAT ERROR) response. DNS server performance and network bandwidth will both be improved by upgrading the DNS server at %2 to a run as either a Windows 2000 DNS server or another IXFR-compatible DNS server implementation.

6536
MessageId=6536

Severity=Error

SymbolicName=DNS_EVENT_IXFR_BAD_RESPONSE

Invalid IXFR (Incremental Zone Transfer) response from master DNS server at %2 during attempted incremental transfer of zone %1. Check the DNS server at %2, and verify its is running as a Windows 2000 DNS server or another IXFR-compatible DNS server implementation.

6701
MessageId=6701

Severity=Success

SymbolicName=DNS_EVENT_UPDATE_DS_PEERS_SUCCESS

DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with it, they have been updated with the new records through dynamic update.

6702
MessageId=6702

Severity=Error

SymbolicName=DNS_EVENT_UPDATE_DS_PEERS_FAILURE

DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error should be ignored. If this DNS server's Active Directory replication partners do not have the correct IP address for this server, they will be unable to replicate with it.

To insure proper replication, follow these steps:


 * 1) Find this server's Active Directory replication partners that run the DNS server.
 * 2) Open DNS Manager and connect in turn to each of the replication partners.
 * 3) On each server, check the host (A record) registration for THIS server.
 * 4) Delete any A records that do NOT correspond to IP addresses of this server.
 * 5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the Active Directory DNS server you are updating.)
 * 6) It is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.

