Your DHCP server that is running Microsoft Windows Server 2003 may not unregister DNS PTR resource records for expired IP address
leases. When this condition occurs, you may experience the following symptoms:
- A backlog of expired leases accumulates on the DHCP server.
- Network programs cannot connect to network resources.
This problem may occur if the number of expired IP address leases is greater than the maximum number that is specified by the queue limit. When the queue limit is reached, remaining records are not processed until the next registration interval. With this hotfix, you can set the queue limit.
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.
No prerequisites are
You must stop and then restart the DHCP Server service after you apply this hotfix.
This hotfix does not replace any other hotfixes.
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.IA-64
Date Time Version Size File name
25-Feb-2004 17:12 5.2.3790.132 676,864 Dhcpssvc.dll IA-64
25-Feb-2004 17:16 5.2.3790.132 259,584 Wdhcpssvc.dll x86
19-Jan-2004 22:53 271 Branches.inf
25-Feb-2004 17:23 10,119 Kb837061.cat
25-Feb-2004 17:18 354 Updatebr.inf
25-Feb-2004 17:19 8,393 Update_rtmqfe.inf
Date Time Version Size File name
25-Feb-2004 17:16 5.2.3790.132 259,584 Dhcpssvc.dll
19-Jan-2004 22:54 271 Branches.inf
25-Feb-2004 17:23 9,766 Kb837061.cat
25-Feb-2004 17:17 354 Updatebr.inf
25-Feb-2004 17:18 6,568 Update_rtmqfe.inf
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section of this article.
After you apply this hotfix, you can use a registry value to set the queue limit. To set the queue limit, follow these steps:
- Click Start, and then click Run.
- Type regedit in the Open box, and then click OK.
- Locate the following registry subkey:
- Right-click Parameters, point to New, and then click DWORD Value.
- Type DynamicDNSQueueLength for the value name, and then press ENTER.
- Double-click DynamicDNSQueueLength, and then type a value for the queue limit. For example, type 2048.
Note In Windows Server 2008 and Windows Server 2008 R2, the value of DynamicDNSQueueLength can be up to 65536.
- Quit Registry Editor.
- Click Start, point to Administrative Tools, and then click Services.
- Stop and then restart the DHCP Server service.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
Description of the standard terminology that is used to describe Microsoft software updates