You install the Domain Name System (DNS) Server role on a computer that is running Windows Server 2008 R2.
You create a large DNS zone on the computer. The background zone loading feature is used to load the DNS zone.
You restart the DNS Server service or the computer.
You send a multi-label name resolution request for an existing name to the DNS zone immediately after the DNS Server service restarts.
In this scenario, the DNS Server service does not resolve the name resolution request. However, the related record exists in the DNS zone.
For example, you try to resolve the "a.b.contoso.com" name from the "contoso.com" zone. In this scenario, the DNS Server service does not retrieve the record that is not yet loaded from Active Directory Domain Services (AD DS). Therefore, the DNS Server service sends a "no such name" response.
Note This issue occurs only when the DNS Server service loads the DNS zone. This issue does not occur after the zone is loaded.
This issue occurs because the DNS Server service handles multi-label name resolution request incorrectly when the background zone loading feature is used to load the DNS zone.
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 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, visit the following Microsoft Web site:
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.
To apply this hotfix, you must be running Windows Server 2008 R2. Additionally, you must have the DNS Server role installed.
To use the hotfix, you do not have to change the registry.
You must restart the computer after you apply this hotfix.
Note If you stop the DNS Server service before you install this hotfix, you do not have to restart the computer.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
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 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 maintaining the state of the updated component. 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
To work around this issue, run the following command to disable the background zone loading feature on the affected DNS server:
dnscmd /Config /DsMinimumBackgroundLoadThreads 0
Note If the background zone loading feature is disabled, the DNS Server service does not respond to name resolution requests until the zones are loaded completely. If you host large zones, the loading process may require several minutes.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For more information about the background zone loading feature, visit the following Microsoft website: