Name resolution is broken between a Windows Server 2003-based parent domain and its child domains, and among the child domains, when scavenging is configured on both the parent and child DNS zones

Support for Windows Server 2003 ended on July 14, 2015

Microsoft ended support for Windows Server 2003 on July 14, 2015. This change has affected your software updates and security options. Learn what this means for you and how to stay protected.

This article has been archived. It is offered "as is" and will no longer be updated.
Consider the following scenario:
  • A Windows Server 2003-based partent domain and some Windows Server 2003-based child domains exist in an Active Directory environment, or A Windows Server 2008-based partent domain and some Windows Server 2008-based child domains exist in an Active Directory environment.
  • The DNS zone of the parent domain is configured to use the To all DNS servers in the Active Directory forest replication option.
  • Scavenging is configured in the parent DNS zone.
  • The DNS zones for child domains are configured to use the To all DNS servers in the Active Directory domain replication option.
  • Scavenging is also configured in child DNS zones.
In this scenario, the DNS delegation records may be scavenged from the parent domain DNS zone. After these records are scavenged, name resolution functionality is broken between the parent domain and the child domains. Name resolution is also broken among child domains.

Additionally, in the Properties box of the delegated domain, the IP addresses of the authoritative servers for the domain appear with an asterisk (*). The glue records become unknown on the DNS console.
When a DNS server in a child domain starts, the server loads its parent zone. However, the server incorrectly sets a time stamp on the delegation DNS record. This change is then replicated to DNS servers in the parent domain. Because the delegation DNS record is never updated, the record is scavenged when the scavenging interval expires.

After the delegation DNS record is deleted, communication between the parent domain DNS server and child domain DNS server is broken. Similarly, communication among child domain DNS servers is also broken in this scenario.

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. 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, the computer must have Windows Server 2003 Service Pack 1,Windows Server 2003 Service Pack 2, or Windows Server 2008 installed.

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows Server 2003 SP1, x86-based versions
File nameFile versionFile sizeDateTimePlatformSP requirement
Dnsperf.hNot Applicable6,64226-Apr-200804:36Not ApplicableSP1
Dnsperf.iniNot Applicable11,59726-Apr-200804:36Not ApplicableSP1
Tcpip6.sys5.2.3790.3161225,98420-Jun-200810:04Not ApplicableSP1
Windows Server 2003 SP2, x86-based versions
File nameFile versionFile sizeDateTimePlatformSP requirement
Dnsperf.hNot Applicable6,64226-Apr-200804:36Not ApplicableSP2
Dnsperf.iniNot Applicable11,59726-Apr-200804:36Not ApplicableSP2
Tcpip6.sys5.2.3790.4318234,49620-Jun-200810:19Not ApplicableSP2
Windows Server 2003 SP1, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.2.3790.2771362,49625-Jun-200900:14IA-64SP1Not Applicable
Afd.sys5.2.3790.3229584,19225-Jun-200900:14IA-64SP1Not Applicable
Dns.exe5.2.3790.33671,148,92825-Jun-200900:14IA-64SP1Not Applicable
Dnsperf.dll5.2.3790.329526,62425-Jun-200900:14IA-64SP1Not Applicable
Dnsperf.hNot Applicable6,64225-Jun-200900:14Not ApplicableSP1Not Applicable
Dnsperf.iniNot Applicable11,59725-Jun-200900:14Not ApplicableSP1Not Applicable
Mswsock.dll5.2.3790.3161784,89625-Jun-200900:15IA-64SP1Not Applicable
Tcpip.sys5.2.3790.31611,308,67225-Jun-200900:15IA-64SP1Not Applicable
Tcpip6.sys5.2.3790.3161737,02425-Jun-200900:15Not ApplicableSP1Not Applicable
W03a2409.dll5.2.3790.336051,71225-Jun-200900:15IA-64SP1Not Applicable
Windows Server 2003 SP2, Itanium-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4392584,19225-Jun-200900:16IA-64SP2Not Applicable
Dns.exe5.2.3790.45381,150,46425-Jun-200900:16IA-64SP2Not Applicable
Dnsperf.dll5.2.3790.446026,62425-Jun-200900:17IA-64SP2Not Applicable
Dnsperf.hNot Applicable6,64225-Jun-200900:17Not ApplicableSP2Not Applicable
Dnsperf.iniNot Applicable11,59725-Jun-200900:17Not ApplicableSP2Not Applicable
Mswsock.dll5.2.3790.4318789,50425-Jun-200900:17IA-64SP2Not Applicable
Tcpip.sys5.2.3790.43181,310,20825-Jun-200900:17IA-64SP2Not Applicable
Tcpip6.sys5.2.3790.4318764,41625-Jun-200900:18Not ApplicableSP2Not Applicable
W03a3409.dll5.2.3790.452941,98425-Jun-200900:18IA-64SP2Not Applicable
Windows Server 2003, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
6to4svc.dll5.2.3790.2771124,41625-Jun-200900:17x64SP1Not Applicable
Afd.sys5.2.3790.3229299,52025-Jun-200900:18x64SP1Not Applicable
Dns.exe5.2.3790.3367780,28825-Jun-200900:18x64SP1Not Applicable
Dnsperf.dll5.2.3790.329514,33625-Jun-200900:18x64SP1Not Applicable
Dnsperf.hNot Applicable6,64225-Jun-200900:18Not ApplicableSP1Not Applicable
Dnsperf.iniNot Applicable11,59725-Jun-200900:18Not ApplicableSP1Not Applicable
Mswsock.dll5.2.3790.3161491,52025-Jun-200900:18x64SP1Not Applicable
Tcpip.sys5.2.3790.3161829,95225-Jun-200900:19x64SP1Not Applicable
Tcpip6.sys5.2.3790.3161363,13625-Jun-200900:19x64SP1Not Applicable
W03a2409.dll5.2.3790.336053,24825-Jun-200900:19x64SP1Not Applicable
Windows Server 2003 SP2, x64-based versions
File nameFile versionFile sizeDateTimePlatformSP requirementService branch
Afd.sys5.2.3790.4392292,35225-Jun-200900:24x64SP2Not Applicable
Dns.exe5.2.3790.4538780,28825-Jun-200900:24x64SP2Not Applicable
Dnsperf.dll5.2.3790.446014,33625-Jun-200900:24x64SP2Not Applicable
Dnsperf.hNot Applicable6,64225-Jun-200900:24Not ApplicableSP2Not Applicable
Dnsperf.iniNot Applicable11,59725-Jun-200900:24Not ApplicableSP2Not Applicable
Mswsock.dll5.2.3790.4318493,05625-Jun-200900:25x64SP2Not Applicable
Tcpip.sys5.2.3790.4318784,89625-Jun-200900:25x64SP2Not Applicable
Tcpip6.sys5.2.3790.4318375,80825-Jun-200900:25x64SP2Not Applicable
W03a3409.dll5.2.3790.452943,52025-Jun-200900:25x64SP2Not Applicable
Windows Server 2008, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot Applicable3,17901-Apr-200918:54Not Applicable
Dns.exe6.0.6001.22527510,46418-Sep-200920:40x86 Applicable60901-Apr-200918:54Not Applicable
Cache.dnsNot Applicable3,17903-Apr-200920:42Not Applicable
Dns.exe6.0.6002.22229510,97618-Sep-200910:07x86 Applicable60903-Apr-200920:42Not Applicable
Windows Server 2008, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Cache.dnsNot Applicable3,17901-Apr-200915:54Not Applicable
Dns.exe6.0.6001.22527638,46418-Sep-200921:46x64 Applicable60901-Apr-200915:54Not Applicable
Cache.dnsNot Applicable3,17903-Apr-200920:39Not Applicable
Dns.exe6.0.6002.22229638,97618-Sep-200910:17x64 Applicable60903-Apr-200920:39Not Applicable
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, 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
dns scavenging aging star unknown

Article ID: 960898 - Last Review: 01/15/2015 19:22:36 - Revision: 4.0

  • Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
  • Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
  • Microsoft Windows Server 2003, Datacenter x64 Edition
  • Microsoft Windows Server 2003, Enterprise x64 Edition
  • Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
  • Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
  • Microsoft Windows Server 2003, Standard x64 Edition
  • Microsoft Windows Server 2003, Standard Edition (32-bit x86)
  • Windows Server 2008 Datacenter without Hyper-V
  • Windows Server 2008 Enterprise without Hyper-V
  • Windows Server 2008 Standard without Hyper-V
  • Windows Server 2008 Datacenter
  • Windows Server 2008 Enterprise
  • Windows Server 2008 Standard
  • kbnosurvey kbarchive kbautohotfix kbexpertiseadvanced kbfix kbsurveynew kbqfe KB960898