Computer cannot be registered in DNS when you renew the IP address in Windows 8.1 or Windows Server 2012 R2

Applies to: Windows 8.1 EnterpriseWindows 8.1 ProWindows 8.1

Summary


This article describes an issue when you renew the IP address in Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. The issue is resolved in update rollup 2962409, or in hotfix 2964536 that is described in this article and has a prerequisite.

Symptoms


Consider the following scenario:

  • You have a computer that is running Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2.
  • The computer uses the Dynamic Host Configuration Protocol (DHCP) to obtain an IP address.
  • The DHCP server is configured to always automatically update the authoritative Domain Name System (DNS) servers together with the host A and PTR records of DHCP clients.
  • You configure a disjoint namespace.
  • You try to perform an ipconfig /renew command on the DHCP client computer.
In this scenario, the DHCP client cannot send the fully qualified domain name (FQDN) to the DHCP server in the renew message. Therefore, the DHCP server cannot register the FQDN of the DHCP client within the appropriate DNS namespace.

Cause


This issue occurs because the GetDomainNameOption function handles data incorrectly and returns some junk data as part of the data buffer.

Resolution


To resolve this issue, install update rollup 2962409, or install the hotfix that is described in this article.

Update information

For more information about how to obtain this update rollup package, click the following article number to view the article in the Microsoft Knowledge Base:
2962409  Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014

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.

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, submit a request to 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 website: 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, you must first install the update 2919355 on Windows RT 8.1, Windows 8.1, or Windows Server 2012 R2. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

2919355 Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update rollup: June 2014


Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Status


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

Additional file information

Additional file information for Windows 8.1 and for Windows Server 2012 R2

Additional files for all supported x86-based versions of Windows 8.1
File propertyValue
File nameX86_86d9030de85c3247352dc3065770b1cf_31bf3856ad364e35_6.3.9600.17111_none_c77df0c002bdae0e.manifest
File versionNot applicable
File size710
Date (UTC)30-Apr-2014
Time (UTC)19:17
File nameX86_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17111_none_01dd0a17746e5d14.manifest
File versionNot applicable
File size24,762
Date (UTC)30-Apr-2014
Time (UTC)10:06
Additional files for all supported x64-based versions of Windows 8.1 and of Windows Server 2012 R2
File propertyValue
File nameAmd64_86d9030de85c3247352dc3065770b1cf_31bf3856ad364e35_6.3.9600.17111_none_239c8c43bb1b1f44.manifest
File versionNot applicable
File size712
Date (UTC)30-Apr-2014
Time (UTC)19:50
File nameAmd64_fe343731617907a891db7dc29b0fb0c4_31bf3856ad364e35_6.3.9600.17111_none_c0bc1e93916ab3cf.manifest
File versionNot applicable
File size714
Date (UTC)30-Apr-2014
Time (UTC)19:50
File nameAmd64_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17111_none_5dfba59b2ccbce4a.manifest
File versionNot applicable
File size24,770
Date (UTC)30-Apr-2014
Time (UTC)11:15
File nameX86_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17111_none_01dd0a17746e5d14.manifest
File versionNot applicable
File size24,762
Date (UTC)30-Apr-2014
Time (UTC)10:06
Additional files for Windows RT 8.1
File propertyValue
File nameArm_cdf72ae16389b638cf9d33440b28d27b_31bf3856ad364e35_6.3.9600.17111_none_a929cb093eedd805.manifest
File versionNot applicable
File size710
Date (UTC)30-Apr-2014
Time (UTC)19:21
File nameArm_microsoft-windows-dhcp-client-dll-minwin_31bf3856ad364e35_6.3.9600.17111_none_01df7c6f746b7bda.manifest
File versionNot applicable
File size24,762
Date (UTC)30-Apr-2014
Time (UTC)08:58
For more information about disjoint namespace , go to the following Microsoft website: