Microsoft KB Archive/883512

= FIX: The DNS Client service uses the first IP address that the DNS server returns, even if the IP address is not on the local subnet, when you access the DNS server from a Windows Server 2003-based client =

Article ID: 883512

Article Last Modified on 7/24/2007

-

APPLIES TO


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

-





SYMPTOMS
Consider the following scenario:
 * You access a Domain Name System (DNS) server from a Microsoft Windows Server 2003-based client.
 * The DNS server has multiple IP addresses.
 * The DNS server is set to use the round robin feature to return the IP addresses to the clients.
 * The IP addresses and the subnet masks that are registered to the DNS server use the Classless Internet Domain Routing (CIDR) format. For example, the IP addresses are native class A addresses that have native class B subnet masks or native class C subnet masks.

In this scenario, the DNS Client service uses the first IP address that the DNS server returns, even if the IP address is not on the local subnet.



CAUSE
This issue occurs because the DNS Client service does not use subnet prioritization in Windows Server 2003.



Service pack information
To resolve this problem, obtain the latest service pack for Windows Server 2003. 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

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 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
No prerequisites are required to install this hotfix.

Restart requirement
You must restart the computer after you apply this hotfix. However, you can restart the computer later. To restart the computer later, click to select the Do not restart now check box before you click Finish when you install the 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 tool in Control Panel.

Windows Server 2003, x86-based versions
  Date         Time   Version            Size    File name --  19-Mar-2005  23:06  5.2.3790.292      151,040  Dnsapi.dll

Windows Server 2003, Itanium-based versions
  Date         Time   Version            Size    File name        Platform 19-Mar-2005 07:07  5.2.3790.292      416,256  Dnsapi.dll       IA-64 19-Mar-2005 07:06  5.2.3790.292      151,040  Wdnsapi.dll      x86



STATUS
Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the &quot;Applies to&quot; section. This bug was corrected in Microsoft Windows Server 2003 Service Pack 1.

