Symptoms
Consider the following scenario:
-
You have a DNS server that's running Windows Server 2012 R2 or Windows Server 2008 R2 Service Pack 1 (SP1).
-
You perform an incremental zone transfer (IXFR) by using a DNS BIND implementation to this DNS server.
In this scenario, you discover that the Windows DNS server incorrectly parses some client computer records, such as address (A) resource records and text (TXT) resource records. Additionally, incorrect data such as IP addresses are attached to the zone's name, where the zone's name is the same as the name of the parent folder.Note This problem does not occur when both DNS servers are Windows DNS servers.
Cause
This problem occurs because Windows DNS incorrectly handles the IXFR requests.
Resolution
To resolve this issue in Windows Server 2012 R2, install update 2919355.To resolve this issue in Windows Server 2008 R2, install the hotfix that is described in this article.
Update information for Windows Server 2012 R2
For more information about how to obtain update 2919355, click the following article number to view the article in the Microsoft Knowledge Base:
2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 Update April, 2014
Hotfix information for Windows Server 2008 R2
A supported hotfix is available from Microsoft Support. 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, go to the following Microsoft website:
http://support.microsoft.com/contactus/?ws=supportNote 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, you must have Service Pack 1 for Windows Server 2008 R2 installed.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any previously released hotfix.
The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information and notesImportant Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
-
The files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table.
Version
Product
SR_Level
Service branch
6.1.760 1. 22xxx
Windows Server 2008 R2
SP1
LDR
-
GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Cache.dns |
Not Applicable |
3,198 |
05-Nov-2010 |
01:52 |
Not Applicable |
|
Dns.exe |
6.1.7601.22500 |
699,392 |
02-Nov-2013 |
01:59 |
x64 |
|
Dnsserver.events.xml |
Not Applicable |
609 |
05-Nov-2010 |
01:52 |
Not Applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Additional file information for Windows Server 2008 R2
Additional files for all supported x64-based versions of Windows Server 2008 R2
|
File name |
Amd64_fd4079354a7937066486c5a0466d87da_31bf3856ad364e35_6.1.7601.22500_none_6d3b33e1509efe09.manifest |
|
File version |
Not Applicable |
|
File size |
710 |
|
Date (UTC) |
02-Nov-2013 |
|
Time (UTC) |
17:41 |
|
Platform |
Not Applicable |
|
File name |
Amd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.22500_none_acbc3dc6064d5e43.manifest |
|
File version |
Not Applicable |
|
File size |
158,131 |
|
Date (UTC) |
02-Nov-2013 |
|
Time (UTC) |
03:26 |
|
Platform |
Not Applicable |
References
or more information, see the DNS architecture topic on the Microsoft TechNet website.Learn about the terminology that Microsoft uses to describe software updates.
