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.

A Windows Server 2008-based DHCP server does not register DNS records for earlier version DHCP clients that do not send option 81 to the DHCP server


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You enable the Dynamic Host Configuration Protocol (DHCP) Server role on a Windows Server 2008-based computer.
  • The following option is enabled on the DHCP server:
    Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0)
  • Some earlier version DHCP clients contact this DHCP server to request or renew their IP addresses. These clients do not support FQDN. Therefore, they do not send option 81 to the DHCP server.
In this scenario, Windows Server 2008-based DHCP server does not register DNS records for these earlier version DHCP clients. Therefore, these clients cannot be accessed by using DNS names.

↑ Back to the top


Cause

The DHCP Server service cannot set the dynamic update flag for these clients. Therefore, the host names of the clients are not registered in the DNS zone.

↑ Back to the top


Resolution

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 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 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.


Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the “Hotfix Request” page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, the computer must be running Windows Server 2008. Additionally, the DHCP Server role must be enabled on the computer.

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.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

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 2008 file information note

The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are
listed separately
. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical to maintaining the state of the updated component. The security catalog files (attributes not listed) are signed with a Microsoft digital signature.
Windows Server 2008, x86-based version
File nameFile versionFile sizeDateTimePlatform
Dhcpserver.events.xmlNot Applicable58118-Dec-200721:00Not Applicable
Dhcpssvc.dll6.0.6001.22375490,49612-Feb-200905:41x86
Windows Server 2008, x64-based version
File nameFile versionFile sizeDateTimePlatform
Dhcpserver.events.xmlNot Applicable58118-Dec-200721:00Not Applicable
Dhcpssvc.dll6.0.6001.22375618,49612-Feb-200906:15x64

↑ Back to the top


Workaround

To work around the issue, you must manually register DNS records for these clients every time that they change their IP addresses.

↑ 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

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


Additional files for all supported x86-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Package_for_kb967363_sc_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42512-Feb-200918:58Not Applicable
Package_for_kb967363_sc~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,42212-Feb-200918:58Not Applicable
Package_for_kb967363_server_0~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,40712-Feb-200918:58Not Applicable
Package_for_kb967363_server~31bf3856ad364e35~x86~~6.0.1.0.mumNot Applicable1,43012-Feb-200918:58Not Applicable
X86_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6001.22375_none_294ccc3ab0dcbdc2.manifestNot Applicable141,65412-Feb-200906:05Not Applicable
Additional files for all supported x64-based versions of Windows Server 2008
File nameFile versionFile sizeDateTimePlatform
Amd64_microsoft-windows-dhcpserverruntime_31bf3856ad364e35_6.0.6001.22375_none_856b67be693a2ef8.manifestNot Applicable141,69812-Feb-200906:39Not Applicable
Package_for_kb967363_sc_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43312-Feb-200918:58Not Applicable
Package_for_kb967363_sc~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43012-Feb-200918:58Not Applicable
Package_for_kb967363_server_0~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,41512-Feb-200918:58Not Applicable
Package_for_kb967363_server~31bf3856ad364e35~amd64~~6.0.1.0.mumNot Applicable1,43812-Feb-200918:58Not Applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 967363
Revision : 1
Created on : 1/7/2017
Published on : 10/7/2011
Exists online : False
Views : 152