Symptoms
Consider the following scenario:
-
You have a DNS server that is running Windows Server 2008 or later versions.
-
The DNS server provides DNS services for the Internet telephony system.
-
The Internet telephony system uses the Name Authority Pointer (NAPTR) records to locate Session Initiation Protocol (SIP) services for telephones.
-
The DNS server compresses the DNS NAPTR records before the records are sent on the wire.
-
The telephony equipment or the other downstream clients decompress the NAPTR records.
In this scenario, the telephony equipment or the other downstream clients receive errors.
How to obtain this update or hotfix
To resolve this issue, we have released update rollup and a hotfix for Windows Server 2012 R2.
Before you install this hotfix, check the prerequisite of the hotfix.
The update rollup fixes many other issues in addition to the issue that the hotfix fixes. We recommend that you use the update rollup. The update rollup is larger than the hotfix. Therefore, the update rollup takes longer to download.
Note There is no hotfix for Windows Server 2008, Windows Server 2008 R2, or Windows Server 2012. We recommend that you upgrade the server to Windows Server 2012 R2 to apply this hotfix.
Update for Windows Server 2012 R2
The following update rollup is available.
For Windows Server 2012 R2
Hotfix for Windows Server 2012 R2
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 this specific problem.
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, submit a request to 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 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 first install update 2919355 in Windows 8.1 or Windows Server 2012 R2. For more information, 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
Registry information
To use the hotfix in this package, you do not have to make any changes to the registry.
Restart requirement
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
More Information
For more information about software update terminology, 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.
The global 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 2012 R2 file information and notesImportant Windows 8.1 hotfixes and Windows Server 2012 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 8.1/Windows Server 2012 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, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
Version
Product
Milestone
Service branch
6.3.960 0.17xxx
Windows Server 2012 R2
RTM
GDR
-
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information" section. MUM, MANIFEST, and the associated security catalog (.cat) files, are very 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 2012 R2
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Cache.dns |
Not applicable |
3,198 |
18-Jun-2013 |
14:43 |
Not applicable |
|
Dns.exe |
6.3.9600.17324 |
1,705,984 |
23-Aug-2014 |
05:32 |
x64 |
|
Dnsserver.events.xml |
Not applicable |
609 |
18-Jun-2013 |
14:43 |
Not applicable |
Additional file information
Additional file information for Windows Server 2012 R2
Additional files for all supported x64-based versions of Windows Server 2012 R2
|
File property |
Value |
|---|---|
|
File name |
Amd64_69e95321b30e891d17e507e6712751ab_31bf3856ad364e35_6.3.9600.17324_none_d808637d0763b7e6.manifest |
|
File version |
Not applicable |
|
File size |
710 |
|
Date (UTC) |
23-Aug-2014 |
|
Time (UTC) |
21:51 |
|
Platform |
Not applicable |
|
File name |
Amd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.3.9600.17324_none_3f050e40aa5b117a.manifest |
|
File version |
Not applicable |
|
File size |
260,624 |
|
Date (UTC) |
23-Aug-2014 |
|
Time (UTC) |
08:07 |
|
Platform |
Not applicable |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
