The information in this article applies to:
SYMPTOMSIf a Windows NT 4.0 DNS server contains an invalid CNAME RR record (see RFC 1034), the following two problems may occur:
CAUSE
This problem is caused by the following invalid Resource Record that is
originally coming from a Digital UNIX server running BIND DNS 4.9.4-P1:
RESOLUTIONRemove the invalid CNAME RR. STATUSMicrosoft has confirmed this to be a problem in Windows NT version 4.0. We are researching this problem and will post new information here in the Microsoft Knowledge Base as it becomes available. MORE INFORMATION
While Windows NT shows the invalid entry by line number (DNS event ID 203:
DNS server could not parse database file x line number y), BIND to Windows
NT zone transfer does not generate an error, but does not complete either.
In a network trace, you see Windows NT TCP resetting the connection during
zone transfer.
The domain system provides such a feature using the canonical name (CNAME) RR. A CNAME RR identifies its owner name as an alias, and specifies the corresponding canonical name in the RDATA section of the RR. If a CNAME RR is present at a node, no other data should be present; this ensures that the data for a canonical name and its aliases cannot be different. This rule also insures that a cached CNAME can be used without checking with an authoritative server for other RR types. Additional query words: domain name system request comments comment
Keywords : kbnetwork kbbug4.00 nttcp |
Last Reviewed: February 5, 1999 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |