A DNS zone transfer between two Windows Server 2003-based DNS servers generates incomplete zone data when the DNS transfer process stops unexpectedly

When a Domain Name System (DNS) zone transfer process between two Windows Server 2003-based DNS servers stops unexpectedly because of an issue on the master server, the transfer process generates incomplete zone data on the secondary server. Users may encounter network-related exception errors if they use the secondary server to perform name resolutions.

For example, this issue may occur when the master server encounters a power failure or a hardware failure.

This problem occurs because no transaction logging mechanism exists during the DNS zone transfer process. If this process is stopped by an exception, incomplete zone data may be generated. However, the DNS server is not aware of the problem.

Hotfix information for Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, the computer must have Windows Server 2003 Service Pack 1 or Service Pack 2 installed.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Windows Server 2003 Service Pack 1, x86-based version

Windows Server 2003 Service Pack 2, x86-based version

Windows Server 2003 SP1, Itanium-based version

Windows Server 2003 SP2, Itanium-based version

Windows Server 2003, x64-based version

Windows Server 2003 SP2, x64-based version

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

A zone transfer may occur in any of the following scenarios:

• The refresh interval expires for the zone.
• A master server notifies a secondary server of zone changes.
• The DNS Server service is started at a secondary server for the zone.
• The DNS console is used at a secondary server for the zone to manually start a transfer from its master server.

Zone transfers are always started at the secondary server for a zone and sent to their configured master servers. The master servers act as the source for the zone. Master servers can be any other DNS server that loads the zone, such as the primary server for the zone or another secondary server. When the master server receives the request for the zone, the master server can reply with either a partial transfer or a full transfer of the zone to the secondary server.

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: