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

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.

Prerequisites

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

Windows Server 2003 SP2, x86-based versions

Windows Server 2003 SP1, Itanium-based versions

Windows Server 2003 SP2, Itanium-based versions

Windows Server 2003, x64-based versions

Windows Server 2003 SP2, x64-based versions

Windows Server 2008, x86-based versions

Windows Server 2008, x64-based versions

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

For more information, click the following article number to view the article in the Microsoft Knowledge Base: