DNS Client Does Not Try All Servers in DNS Service List (195611)

The information in this article applies to:

Microsoft Windows NT Workstation 4.0
Microsoft Windows NT Server 4.0
Microsoft Windows NT Server, Enterprise Edition 4.0

This article was previously published under Q195611

SYMPTOMS

When a DNS query is made and the query returns an error such as server failure (rcode 2), the other servers in the list were not queried. The failure was passed back to the requester even though querying another server in the list could successfully complete the query.

CAUSE

The only time secondary servers were queried, was when no response is received from the primary server in the server list.

RESOLUTION

To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:

http://www.microsoft.com/windows/servicepacks/ -or-
152734 how to obtain the latest windows nt 4.0 service pack

For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://support.microsoft.com/directory/overview.asp

STATUS

Microsoft has confirmed this to be a problem in Windows NT version 4.0. This problem was first corrected in Windows NT version 4.0 Service Pack 5.

MORE INFORMATION

The DNS query algorithm has been modified to attempt other servers in the server list if an error is received from a server that may be resolved by trying another server in the list. The new algorithm will retry servers until:

The name query is answered successfully.
An authoritative answer is received from a server that the requested host does not exists (rcode 3).
The server list is exhausted.

Modification Type:	Minor	Last Reviewed:	9/23/2005
Keywords:	kbHotfixServer kbQFE kbbug kbfix kbQFE KB195611