A DNS zone transfer between a BIND DNS server and a Windows Server 2003-based DNS server does not work when the BIND DNS server acts as a primary server (912233)
The information in this article 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
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
- 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
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard Edition
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
CAUSEThis 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. RESOLUTIONHotfix informationA supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Windows Server 2003 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site: Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question. Prerequisites No prerequisites are required. Restart requirementYou do not have to restart the computer after you apply this hotfix. Hotfix replacement informationThis 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 |
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 |
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 |
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 |
WORKAROUNDTo work around this problem, modify the BIND configuration file by adding the notify-source * port 53entry in the file.STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Modification Type: | Minor | Last Reviewed: | 7/26/2006 |
---|
Keywords: | kbQFE kbHotfixServer kbWinServ2003SP1fix kbWinServ2003preSP1fix kbBug kbfix kbpubtypekc KB912233 kbAudITPRO |
---|
|