DetailPage-MSS-KB

Microsoft small business knowledge base

Article ID: 2550719 - Last Review: May 31, 2013 - Revision: 6.0

Hotfix Download Available
View and request hotfix downloads
 

On This Page

Symptoms

Consider the following scenario:
  • You are in a network environment.
  • You have a DNS server (server A) that is running Windows Server 2008 R2 and that hosts a DNS zone.
  • You enable Windows Internet Name Service (WINS) forward lookup on the DNS zone on server A.
  • You have another DNS server (server B) that is running Windows Server 2008 R2 and that has a forwarder to server A.
  • You send a query to the forwarding DNS server (server B).
  • The query is forwarded to server A, and then is resolved by using WINS forward lookup successfully.
  • You wait for the Time to Live (TTL) value to expire and then send the same query to server B again.

    Note The default TTL expiration value is 15 minutes.
In this scenario, server B receives the following error message from server A:
Name Error 3
Note This issue occurs only between DNS servers that are running Windows Server 2008 R2 and that have the extension mechanisms for DNS (EDNS) probes feature enabled by default.

Resolution

This hotfix is also available at Microsoft Update Catalog (http://catalog.update.microsoft.com/v7/site/Search.aspx?q=2550719)

Hotfix information

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 Web site:
http://support.microsoft.com/contactus/?ws=support (http://support.microsoft.com/contactus/?ws=support)
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, you must be running one of the following operating systems:
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932  (http://support.microsoft.com/kb/976932/ ) Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

Collapse this imageExpand this image
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 2008 R2 file information notes
Important 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.
    Collapse this tableExpand this table
    VersionProductSR_LevelService branch
    6.1.760 0 . 21xxxWindows Server 2008 R2RTMLDR
    6.1.760 1 . 22xxxWindows Server 2008 R2SP1LDR
  • 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.

Version 1 (Fix367430)

For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot Applicable3,19810-Jun-200920:31Not Applicable
Dns.exe6.1.7600.21418697,85607-Jan-201303:52x64
Dnsserver.events.xmlNot Applicable60910-Jun-200920:31Not Applicable
Cache.dnsNot Applicable3,19805-Nov-201001:52Not Applicable
Dns.exe6.1.7601.22211699,39207-Jan-201303:35x64
Dnsserver.events.xmlNot Applicable60905-Nov-201001:52Not Applicable
Note You may experience the following issue after you apply version 1 of this hotfix. To fix this issue, apply version 2 (Fix423384) of this hotfix.

Assume that you configure a DNS Primary Zone (for example, contoso.com) to use WINS lookup, and then you create a subdomain (for example, test.contoso.com) inside ithe DNS pimary zone. When you query for a subdomain that does not exist (for example test.test.contoso.com), you receive SUCCESS instead of NXDOMAIN.

Version 2 (Fix423384)

For all supported x64-based versions of Windows Server 2008 R2
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot Applicable3,19810-Jun-200920:31Not Applicable
Dns.exe6.1.7600.21418697,85607-Jan-201303:52x64
Dnsserver.events.xmlNot Applicable60910-Jun-200920:31Not Applicable
Cache.dnsNot Applicable3,19805-Nov-201001:52Not Applicable
Dns.exe6.1.7601.22211699,39207-Jan-201303:35x64
Dnsserver.events.xmlNot Applicable60905-Nov-201001:52Not Applicable
Collapse this imageExpand this image

Workaround

To work around this issue, disable the EDNS probes feature. To do this, at command prompt, type the following command, and then press Enter:
dnscmd /config /EnableEDNSProbes 0

Status

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

More information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684  (http://support.microsoft.com/kb/824684/ ) Description of the standard terminology that is used to describe Microsoft software updates
For more information about another issue that occurs because of EDNS0 functionality, click the following article number to view the article in the Microsoft Knowledge Base:
832223   (http://support.microsoft.com/kb/832223 / ) Some DNS name queries are unsuccessful after you deploy a Windows Server 2003 or Windows Server 2008 R2-based DNS server

Additional file information

Collapse this imageExpand this image

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2 (Version 1)
Collapse this tableExpand this table
File nameAmd64_50ae1fa8e47c3a58977bfa7454d8d2b2_31bf3856ad364e35_6.1.7601.22211_none_37a1210401993a43.manifest
File versionNot Applicable
File size710
Date (UTC)07-Jan-2013
Time (UTC)10:16
PlatformNot Applicable
File nameAmd64_87965ae87b83bc7b1c79a91e0c478a5e_31bf3856ad364e35_6.1.7600.21418_none_f3ac75160457e33f.manifest
File versionNot Applicable
File size710
Date (UTC)07-Jan-2013
Time (UTC)10:16
PlatformNot Applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7600.21418_none_aad30d720927e18b.manifest
File versionNot Applicable
File size158,131
Date (UTC)07-Jan-2013
Time (UTC)06:27
PlatformNot Applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.22211_none_acb2687206549c16.manifest
File versionNot Applicable
File size158,131
Date (UTC)07-Jan-2013
Time (UTC)06:11
PlatformNot Applicable
File nameUpdate.mum
File versionNot Applicable
File size2,371
Date (UTC)07-Jan-2013
Time (UTC)10:16
PlatformNot Applicable
Additional files for all supported x64-based versions of Windows Server 2008 R2 (Version 2)
Collapse this tableExpand this table
File nameAmd64_50ae1fa8e47c3a58977bfa7454d8d2b2_31bf3856ad364e35_6.1.7601.22211_none_37a1210401993a43.manifest
File versionNot Applicable
File size710
Date (UTC)07-Jan-2013
Time (UTC)10:16
PlatformNot Applicable
File nameAmd64_87965ae87b83bc7b1c79a91e0c478a5e_31bf3856ad364e35_6.1.7600.21418_none_f3ac75160457e33f.manifest
File versionNot Applicable
File size710
Date (UTC)07-Jan-2013
Time (UTC)10:16
PlatformNot Applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7600.21418_none_aad30d720927e18b.manifest
File versionNot Applicable
File size158,131
Date (UTC)07-Jan-2013
Time (UTC)06:27
PlatformNot Applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.22211_none_acb2687206549c16.manifest
File versionNot Applicable
File size158,131
Date (UTC)07-Jan-2013
Time (UTC)06:11
PlatformNot Applicable
Collapse this imageExpand this image

Applies to
  • Windows Server 2008 R2 Standard
  • Windows Server 2008 R2 Foundation
  • Windows Server 2008 R2 Enterprise
  • Windows Server 2008 R2 Datacenter
Keywords: 
kbautohotfix kbqfe kbhotfixserver kbfix kbsurveynew kbexpertiseinter KB2550719
Share
Additional support options
Ask The Microsoft Small Business Support Community
Contact Microsoft Small Business Support
Find Microsoft Small Business Support Certified Partner
Find a Microsoft Store For In-Person Small Business Support