A. I’ve run into the same problem. Under NT, the command you describe causes Nslookup to display all the MX records in the domain, as well as the address (A) record for each returned MX record. Under Win2K, however, Nslookup instead displays the name of the default DNS server and basic information (e.g., primary DNS server, zone file serial number, Time to Live-TTL-value) about the DNS domain zone file.
This situation occurs only when the client is a Win2K system using the Win2K version of Nslookup and when the server you’re querying is an NT 4.0 DNS server. Under these circumstances, a currently undocumented conflict between these two components causes most Nslookup commands to fail.
Two possible workarounds exist. First, you can use Nslookup’s Server command with a variable server_name_or_ip (where server_name_or_ip is the name or IP address of a DNS server) to change the default DNS server to one that isn’t running NT 4.0 DNS. (To make this solution permanent, change the DNS server order in your IP stack so that Nslookup always tries the non-NT 4.0 DNS server first.) Second, you can replace your Win2K system’s version of Nslookup with a copy of the NT 4.0 version, which doesn’t exhibit this odd behavior.