Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Active Directory size increases rapidly on a Windows Server 2003 or Windows Server 2008 R2 domain controller that hosts the DNS Server role


View products that this article applies to.

If you are a Small Business customer, find additional troubleshooting and learning resources at the Support for Small Business site.

↑ Back to the top


Symptoms

The size of the Active Directory database directory information tree (.dit) files increase significantly over time. If you track the change by using the repadmin /showchanges command, you see that most of the growth in file size is contributed by deleted DNS objects.


This may occur in the following scenario:
  • You install the Active Directory Domain Services role and the DNS Server role on a computer that is running Windows Server 2008 R2 or Windows Server 2003.
  • The computer hosts one or more Active Directory-Integrated DNS zones.
  • The Dynamic Updates setting on the General tab of the Properties page of locally held Active Directory-integrated DNS zones is set to Secure only.
  • The same DNS records are registered and deregistered frequently. For example, the same DNS records are registered and deregistered several hundred times per day.

Note The size of the NTDS.dit file may increase faster in the Active Directory database path because of the following factors:
  • Large values for the Tombstone Lifetime setting
  • Large volume of dynamic update record registration that is caused by large populations of Windows and third-party DNS clients, short DHCP lease durations, or code defects that cause third-party devices to register records too often
  • The enabling of the Active Directory Recycle Bin feature

↑ Back to the top


Cause

The issue occurs because of incorrect Active Directory tombstoning of DNS objects.

DNS clients should reuse the existing DNS objects that are marked to be deleted when they register DNS records. The existing DNS objects are usually referred to as “reanimating objects.” However, currently the DNS server service creates a new object for these DNS clients and moves the existing DNS object to the deleted objects container. Over time, this behavior causes the Active Directory DIT file size to increase significantly.

↑ Back to the top


Resolution

After you install the following hotfix, DNS clients can reuse the existing reanimating DNS objects when they register their DNS record.

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 the problem that is 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 website: 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.

Mainstream support for Windows Server 2003 ended on July 13, 2010. A hotfix for this issue exists but is not publicly available. Please review the Microsoft Support Lifecycle policy.

Extended Support

The Extended Support phase follows Mainstream Support for Business and Developer products.
At the supported service pack level, Extended Support includes:
  • Paid support
  • Security update support at no additional cost
  • Non-security related hotfix support requires a separate Extended Hotfix Support Agreement to be purchased (per-fix fees also apply)
Please note:
  • Microsoft will not accept requests for warranty support, design changes, or new features during the Extended Support phase
  • Extended Support is not available for Consumer, Hardware, or Multimedia products
Please contact Microsoft Support for information on how to obtain the hotfix.

Prerequisites

To apply this hotfix, you must be running one of the following operating systems:
  • Windows Server 2003 Service Pack 2 (SP2)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
Additionally, you must have the DNS Server role installed. For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

889100 How to obtain the latest service pack for Windows Server 2003

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

Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To use the hotfix, you do not have to change the registry.

Restart requirement

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.

File information

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 2003 file information notes
  • In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KB2548145.cat) that is signed with a Microsoft digital signature.
For all supported x86-based versions of Windows Server 2003
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4898150,52817-Aug-201115:38x86SP2Not Applicable
Dns.exe5.2.3790.4928451,58403-Nov-201114:21x86SP2Not Applicable
Dnsperf.dll5.2.3790.446011,77617-Feb-200908:12x86SP2Not Applicable
Dnsperf.hNot Applicable6,64208-Jul-201018:34Not ApplicableSP2Not Applicable
Dnsperf.iniNot Applicable11,59708-Jul-201018:34Not ApplicableSP2Not Applicable
Mswsock.dll5.2.3790.4318257,02420-Jun-200819:01x86SP2Not Applicable
Tcpip.sys5.2.3790.4573400,89615-Aug-200908:27x86SP2Not Applicable
Tcpip6.sys5.2.3790.4662248,64010-Feb-201015:51Not ApplicableSP2Not Applicable
W03a3409.dll5.2.3790.471544,54409-Jul-201004:25x86SP2Not Applicable
Wdnsperf.dll5.2.3790.446011,77604-Nov-201107:03x86SP2WOW
Wmswsock.dll5.2.3790.4318234,49604-Nov-201107:03x86SP2WOW
Ww03a3409.dll5.2.3790.471544,54404-Nov-201107:03x86SP2WOW
For all supported x64-based versions of Windows Server 2003
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4898292,35204-Nov-201107:03x64SP2Not Applicable
Dns.exe5.2.3790.4928780,80004-Nov-201107:03x64SP2Not Applicable
Dnsperf.dll5.2.3790.446014,33604-Nov-201107:03x64SP2Not Applicable
Dnsperf.hNot Applicable6,64204-Nov-201107:03Not ApplicableSP2Not Applicable
Dnsperf.iniNot Applicable11,59704-Nov-201107:03Not ApplicableSP2Not Applicable
Mswsock.dll5.2.3790.4318493,05604-Nov-201107:03x64SP2Not Applicable
Tcpip.sys5.2.3790.4573798,20804-Nov-201107:03x64SP2Not Applicable
Tcpip6.sys5.2.3790.4662396,03204-Nov-201107:03x64SP2Not Applicable
W03a3409.dll5.2.3790.471545,05604-Nov-201107:03x64SP2Not Applicable
Wdnsperf.dll5.2.3790.446011,77604-Nov-201107:03x86SP2WOW
Wmswsock.dll5.2.3790.4318234,49604-Nov-201107:03x86SP2WOW
Ww03a3409.dll5.2.3790.471544,54404-Nov-201107:03x86SP2WOW
For all supported IA-64-based versions of Windows Server 2003
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4898584,19204-Nov-201107:03IA-64SP2Not Applicable
Dns.exe5.2.3790.49281,151,48804-Nov-201107:03IA-64SP2Not Applicable
Dnsperf.dll5.2.3790.446026,62404-Nov-201107:03IA-64SP2Not Applicable
Dnsperf.hNot Applicable6,64204-Nov-201107:03Not ApplicableSP2Not Applicable
Dnsperf.iniNot Applicable11,59704-Nov-201107:03Not ApplicableSP2Not Applicable
Mswsock.dll5.2.3790.4318789,50404-Nov-201107:03IA-64SP2Not Applicable
Tcpip.sys5.2.3790.45731,336,32004-Nov-201107:03IA-64SP2Not Applicable
Tcpip6.sys5.2.3790.4662802,68804-Nov-201107:03Not ApplicableSP2Not Applicable
W03a3409.dll5.2.3790.471543,52004-Nov-201107:03IA-64SP2Not Applicable
Wdnsperf.dll5.2.3790.446011,77604-Nov-201107:03x86SP2WOW
Wmswsock.dll5.2.3790.4318234,49604-Nov-201107:03x86SP2WOW
Ww03a3409.dll5.2.3790.471544,54404-Nov-201107:03x86SP2WOW
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 to which that each hotfix applies.
  • 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:
    VersionProductMilestoneService branch
    6.1.760
    0.20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • The MANIFEST files (.manifest) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MANIFEST files and the associated security catalog (.cat) files, are very important to maintaining 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 nameFile versionFile sizeDateTimePlatform
Cache.dnsNot applicable3,19810-Jun-200920:31Not applicable
Dns.exe6.1.7600.20969696,83219-May-201105:54x64
Dnsserver.events.xmlNot applicable60910-Jun-200920:31Not applicable
Cache.dnsNot applicable3,19805-Nov-201001:52Not applicable
Dns.exe6.1.7601.21730697,34419-May-201105:49x64
Dnsserver.events.xmlNot applicable60905-Nov-201001:52Not applicable

↑ Back to the top


Workaround

To work around the issue, change the value of Security updates to None or to Nonsecure and secure in the DNS server zones.

↑ Back to the top


Status

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

↑ Back to the top


More Information

Administrators should install this fix on Windows Server 2003-based or Windows Server 2008 R2-based DNS servers that host Active Directory (AD)-integrated copies of primary zones that receive client updates. Give priority to installing this fix on Windows Server 2003-based and Windows Server 2008 R2-based DNS servers that host AD-integrated primary zones updated by clients over DNS servers whose zones are not updated by clients.

Windows Server 2003-based and Windows Server 2008 R2-based DNS servers that host the RODC role, that host AD-integrated primary zone that has aging enabled, or that host file-based copies of DNS zones are not subjected to this bug and do not require or benefit from this fix because they never adopt the at-risk configuration. 

Installing this hotfix on the relevant servers prevents additional NTDS.DIT growth caused by an accumulation of deleted DNS records on record re-registration. Microsoft recommends that you wait for Active Directory to gracefully purge records as part of the garbage collection process as opposed to reducing the tombstone lifetime setting to accelerate the garbage collection of tombstoned DNS objects.

For more information about the repadmin showchanges command, go tothe following Microsoft website:For more information about DNS tombstone issues, see Microsoft Knowledge Base article 952087: Customized permissions that are applied to DNS records are reset to the default value when these records are deleted and tombstoned on a Windows Server 2003-based DNS server

For more information about the tombstone lifetime for the forest, go tothe following Microsoft website:
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

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_065d593d9101b797f01c2ac02576fe8e_31bf3856ad364e35_6.1.7601.21730_none_6394a86100881bf7.manifest
File versionNot applicable
File size710
Date (UTC)19-May-2011
Time (UTC)20:55
PlatformNot applicable
File nameAmd64_7013e66b791e7749ad22c529a3fdca2d_31bf3856ad364e35_6.1.7600.20969_none_2104ff898fe07770.manifest
File versionNot applicable
File size710
Date (UTC)19-May-2011
Time (UTC)20:55
PlatformNot applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7600.20969_none_aa9e1e66094f5eb9.manifest
File versionNot applicable
File size158,131
Date (UTC)19-May-2011
Time (UTC)18:38
PlatformNot applicable
File nameAmd64_microsoft-windows-dns-server-service_31bf3856ad364e35_6.1.7601.21730_none_ac9be896066592c3.manifest
File versionNot applicable
File size158,131
Date (UTC)19-May-2011
Time (UTC)19:12
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size2,371
Date (UTC)19-May-2011
Time (UTC)20:55
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbexpertiseadvanced, kbsurveynew, kbsmbportal

↑ Back to the top

Article Info
Article ID : 2548145
Revision : 3
Created on : 1/27/2017
Published on : 1/27/2017
Exists online : False
Views : 298