Article ID: 912233
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Datacenter x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003 SP1, when used with:
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
- Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
SYMPTOMS
Consider the following scenario:
A primary Berkeley Internet Name Domain (BIND) DNS server sends a DNS zone transfer notification to a secondary Microsoft Windows Server 2003-based DNS server. The notification is part of the DNS zone transfer process. However, the DNS zone transfer does not work after the Windows Server 2003-based DNS server tries to load the changes from the primary DNS server.
Note The DNS zone transfer does work whenever the refresh interval elapses in the Start of Authority (SOA) record for the DNS zone. Additionally, you may notice that the DNS zone transfer works when you use the following options to initiate a manual zone transfer from a Windows Server 2003-based DNS server:
- Transfer from Master
- Reload from Master
CAUSE
This problem occurs because the Windows Server 2003-based DNS server uses a high port instead of port 53 to complete the following tasks:
- To send an incremental zone transfer (IXFR) DNS query packet to the BIND DNS server.
- To send a full zone transfer (AXFR) DNS query packet to the BIND DNS server.
The BIND DNS server must use the default port 53 to receive the query from the secondary Windows DNS server. When the Windows Server 2003-based DNS server uses a high port to send an IXFR or an AXFR DNS query packet to the BIND DNS server, a receiver is unavailable to receive the query. Therefore, the DNS zone transfer does not work.
RESOLUTION
Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
889100 How to obtain the latest service pack for Windows Server 2003
Hotfix information
Prerequisites
No prerequisites are required.
Restart requirement
You do not have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
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, x86-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Dns.exe | 5.2.3790.455 | 423,936 | 17-Dec-2005 | 01:50 | x86 | None | RTMQFE |
| Dns.exe | 5.2.3790.2594 | 442,368 | 17-Dec-2005 | 05:56 | x86 | SP1 | SP1QFE |
Windows Server 2003, Itanium-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Dns.exe | 5.2.3790.455 | 1,025,024 | 16-Dec-2005 | 17:45 | IA-64 | None | RTMQFE |
| Wdns.exe | 5.2.3790.455 | 423,936 | 16-Dec-2005 | 17:45 | x86 | None | WOW |
| Dns.exe | 5.2.3790.2594 | 1,124,864 | 17-Dec-2005 | 09:22 | IA-64 | SP1 | SP1QFE |
| Wdns.exe | 5.2.3790.2594 | 442,368 | 17-Dec-2005 | 09:22 | x86 | SP1 | WOW |
Windows Server 2003 x64-based versions
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Dns.exe | 5.2.3790.2594 | 758,272 | 17-Dec-2005 | 09:22 | x64 | SP1 | SP1QFE |
| Wdns.exe | 5.2.3790.2594 | 442,368 | 17-Dec-2005 | 09:22 | x86 | SP1 | WOW |
WORKAROUND
To work around this problem, modify the BIND configuration file by adding the notify-source * port 53 entry in the file.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.
MORE INFORMATION
For more information about standard terminology that is used to describe Microsoft software updates, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Technical support for x64-based versions of Microsoft Windows
Your hardware manufacturer provides technical support and assistance for x64-based versions of Windows. Your hardware manufacturer provides support because an x64-based version of Windows was included with your hardware. Your hardware manufacturer might have customized the installation of Windows with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your x64-based version of Windows. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.
For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site:
For product information about x64-based versions of Microsoft Windows Server 2003, visit the following Microsoft Web site:
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinserv2003sp1fix kbwinserv2003presp1fix kbhotfixserver kbwinserv2003sp2fix KB912233
