Lakshman in said:Is there a command line tool to view what computer is
mapped as the MX record for a particular domain? Would the
dnscmd tool let me do that? Any help or pointers in the
right direction would be greatly appreciated.
Lakshman
*************** REPLY SEPARATER ***************Is there a command line tool to view what computer is
mapped as the MX record for a particular domain? Would the
dnscmd tool let me do that? Any help or pointers in the
right direction would be greatly appreciated.
Lakshman
John Coutts in said:*************** REPLY SEPARATER ***************
Nslookup will do the job, but try my DSN client program which is much
easier to use:
ftp://server2.yellowhead.com/utility/ClientDNS.exe
for the self installable version, and ClientDNS.zip for the zip
version.
***************** REPLY SEPARATER *****************I tried it but I got an "Error 10014 Encountered when sending data".
John Coutts in said:***************** REPLY SEPARATER *****************
Error 10014 is a general Winsock error that can occur for a number of
different reasons, but most often because of a bad socket address.
The program uses the Microsoft Winsock Control 6.0. The remote port
is bound to port 53 UDP, and the local port uses the first available
port on the first interface that supports TCP/IP (I have not tested
the program on machines with more than 1 supporting interface). The
program attempts to discover the first default DNS server available
on your machine, and by default uses it as the remote host. You may
actually use any DNS server listed (or add your own) in either
recursive or non-recursive mode.
To narrow down the problem a bit, could you please supply a little
more information? Does the error occur when the program is loaded, or
does it occur when you attempt to send a query? Does it properly
discover your default DNS, which should appear in the DNS Server box?
If you don't care where the answer comes from, use it in the
recursive mode (default). But if want the answer directly from an
authoratative server, use it in the non-recursive mode. Click the
"Root Servers" button and then choose one of the Root Servers. When
you query the root server, it will supply the GTLD (or whatever)
servers. Choosing one of these and re-applying the query will
generally provide the authoratative servers, but you may have to dig
deeper. Choosing one of these and re-applying the query will provide
the authoratative answer. By default, it looks for the "A" record,
but once the authoratative server is found, you can change the record
type (say to MX) and requery.
You may contact me directly if you so desire.
J.A. Coutts
Systems Engineer
MantaNet/TravPro
<[email protected]>
**************** REPLY SEPARATER *****************But when I tried to choose what ClientDNS found originally, the two
separated by a comma, it did NOT work. Is this a bug?
******************** SEPARATER ************************************** REPLY SEPARATER *****************
It certainly sounds like a bug. The program has to dig the information out of
the registry, and unfortunately there are substantial differences in the way in
which the information is stored in the various Operating Systems. The comma
separation method was generally used in the older operating systems, with the
newer operating systems requiring an enumeration of all the interface registry
entries. It is possible that the methods were combined.
What OS and version are you using?
J.A. Coutts
Win 9x uses the comma separated method in a specific location, WinNT
uses the space separated method in a different location, and I have
confirmed that XP reverts back to the comma separated method in each
interface (don't know about 2000 yet).
I have modified the code to use only the first DNS server, and
updated the install files. I have also made just the updated
executive file available.
J.A. Coutts