CAUSE
This issue can occur if the Exchange 2000 Server computer is unable to contact other Exchange 2000 Server computers or the domain controller in the domain. In the sample events in the "Symptoms" section of this article, the primary Domain Name System (DNS) server is a server that is aware of the domain's domain controllers and SERVERX2K-OTHER, which is another Exchange 2000 Server computer in the domain. However, the secondary DNS server is either offline or is unaware of these other servers.
For example, this issue can occur in a test environment if you manually enter the IP address of a test DNS server that is aware of SERVERX2K-OTHER as the primary DNS server of an Exchange 2000 Server computer, and then Dynamic Host Configuration Protocol (DHCP) assigns a production DNS server that is unaware of the SERVERX2K-OTHER Exchange 2000 Server computer and any domain controllers as the secondary DNS server. Whenever network problems prevent the test DNS server from responding in a timely manner, the Exchange 2000 Server computer queries the secondary server. That query does not work, and generates the errors and the warning in the "Symptoms" section of this article.
RESOLUTION
To resolve this issue, set a valid DNS server that has knowledge of the domain controller and the other Exchange 2000 Server computers in the domain as the secondary DNS server.
WORKAROUND
To work around this issue in the sample scenario in the "Cause" section of this article, set the secondary DNS server IP address to the same address as the primary DNS server.
