This article was previously published under Q186820
This article has been archived. It is offered "as is" and will no longer be updated.
With WINS lookup enabled, a Microsoft DNS server returns RCODE=3 when aname exists but the requested type of resource record (RR) is notavailable.
The Microsoft DNS server is returning RCODE=3, which, according to RFC1035, means:
Name Error - Meaningful only for responses from an authoritative name server, this code signifies that the domain name referenced in the query does not exist.
This only occurs when WINS lookup is enabled and the Microsoft DNS serverhas received a response from WINS that states Name Not Found. This ispassed back in error to the original requester as rcode-3 (nxdomain).
BIND 4.9.x and 8.1.x name servers cache the fact that the name does notexist so subsequent queries for other record types that do exist (such as,QTYPE="MX") fail.
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in theMicrosoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition. This problem was first corrected in Windows NT 4.0 Service Pack 4.0 and Windows NT Server 4.0, Terminal Server Edition Service Pack 4.
Section 4.1, Domain Implementation and Specification, of RFC 1035 states
The last three sections have the same format: a possibly empty list ofconcatenated resource records (RRs). The answer section contains RRsthat answer the question; the authority section contains RRs that pointtoward an authoritative name server; the additional records sectioncontains RRs which relate to the query, but are not strictly answers forthe question.
RFC 1034 indicates
When the resolver performs the indicated function, it usually has one ofthe following results to pass back to the client:
One or more RRs giving the requested data. In this case the resolverreturns the answer in the appropriate format.
A name error (NE). This happens when the referenced name does notexist. For example, a user may have mistyped a host name.
A data not found error. This happens when the referenced name exists,but data of the appropriate type does not.
RFC 1035 includes the following
RCODE Response code - this 4 bit field is set as part of responses. Thevalues have the following interpretation:
0 No error condition
1 Format error - The name server was unable to interpret the query.
2 Server failure - The name server was unable to process this querydue to a problem with the name server.
3 Name Error - Meaningful only for responses from an authoritativename server, this code signifies that the domain name referencedin the query does not exist.
4 Not Implemented - The name server does not support the requestedkind of query.
5 Refused - The name server refuses to perform the specifiedoperation for policy reasons. For example, a name server may notwish to provide the information to the particular requester, or aname server may not wish to perform a particular operation (forexample, zoneMockapetris [Page 27] transfer) for particular data.
6-15 Reserved for future use.
The algorithm for operation of a name server specified in RFC 1034, isas follows:
3. Start matching down, label by label, in the zone. The matchingprocess can terminate several ways:
a. If the whole of QNAME is matched, we have found the node.
If the data at the node is a CNAME, and QTYPE doesn'tmatch CNAME, copy the CNAME RR into the answer sectionof the response, change QNAME to the canonical name inthe CNAME RR, and go back to step 1.
Otherwise, copy all RRs which match QTYPE into theanswer section and go to step 6.
According to the specified algorithm, the only time an authoritative nameerror is allowed to be specified is in step 3c. In the case that we have,however, the QNAME did match, so you should copy all the RRs into theanswer section whose TYPE matches QTYPE (in this case zero RRs), and jumpto step 6 which has NO way of setting NXDOMAIN.
Microsoft Windows NT Server 4.0, Terminal Server Edition, Microsoft Windows NT Workstation 4.0 Developer Edition, Microsoft Windows NT Server 4.0 Standard Edition, Microsoft Windows NT Server 4.0 Enterprise Edition