Microsoft KB Archive/938863

= Name resolution may fail on a Windows Server 2003 DNS server if conditional forwarding is configured and if records have different TTL values =

Article ID: 938863

Article Last Modified on 11/29/2007

-

APPLIES TO


 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Web Edition
 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems

-



SYMPTOMS
Consider the following scenario:
 * Conditional forwarding is configured on a Windows Server 2003 Domain Name System (DNS) server.
 * The conditional forwarder points to a DNS server in a parent domain.
 * The zone of the parent domain and the zone of the child domain have different Time to Live (TTL) values that are configured.

In this scenario, the name resolution for a record in the child domain may fail. This problem disappears after you restart the DNS Server service for which conditional forwarding is configured. This problem will occur again after a while.



CAUSE
The DNS Server service in Windows Server 2003 caches DNS records for received queries. However, the TTL values of the name server records (&quot;NS&quot; records), of the Host records (&quot;A&quot; records), and of other records may not match. If the TTL value of the &quot;A&quot; record is much shorter than the TTL value of the &quot;NS&quot; record, this problem occurs after the TTL value of the &quot;A&quot; record expires.

The cache is cleared when the DNS Server service restarts. Therefore, this problem disappears after the DNS Server service restarts. This problem occurs again when the TTL value of the &quot;A&quot; record expires.



Hotfix information
A supported hotfix is now 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 or Windows Server 2003 Service Pack 2 installed on the computer. For more information, 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

Restart requirement
You must restart the computer after you apply this hotfix.

Hotfix replacement information
This hotfix does not replace any other 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 with Service Pack 2, x64-based versions


WORKAROUND
To work around this problem, follow these steps:  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\DNS\Parameters

 On the Edit menu, point to New, and then click DWORD Value. Type LameDelegationTtl, and then press ENTER. Right-click LameDelegationTtl, and then click Modify. Under Base, click Decimal.</li> In the Value data box, type the value that you want, and then click OK.

Note The value that you type inside the Value data box is a TTL value that is measured in seconds. To work around this problem, you must set this TTL value to a value that is smaller than the TTL value of the &quot;A&quot; record. For example, if the TTL value of the &quot;A&quot; record is 1 hour, you can set the registry value to the following value:

1800

This value of 1,800 seconds is equal to 30 minutes.</li> Exit Registry Editor.</li></ol>

<div class="status_section">

STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.

<div class="moreinformation_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 Description of the standard terminology that is used to describe Microsoft software updates

Keywords: kbexpertiseinter kbwinserv2003postsp2fix kbbug kbfix kbhotfixserver kbqfe KB938863

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.