logo
ClientDNS Back to Home Page



ClientDNS is a utility program designed and intended to give you full access to the DNS packets returned from the requested server. DNS packets are very compact and highly cryptic, and because of that, command line utilities like "NSLookUP" will display incomplete interpretted results. ClientDNS returns all the results on separate tabs.

ClientDNS is written in VB6, and is being made available in ZIP format. Installation is usually straight forward, using "setup.exe" to install files extracted from "ClientDNS.cab" as laid out in "setup.lst". It has been tested to be UAC compatible.

Internet standards require DNS servers to accept both UDP and TCP requests. TCP is very seldom used however, and some servers do not accept them due to firewall restrictions on port 53. ClientDNS does not support TCP.

ClientDNS finds and uses your default DNS servers to get the IP addresses of the named servers. Consequently, it cannot be used to troubleshoot your own DNS service unless you manually enter the IP address of the server. Executing the program:

ClientDNS will find your default Nameservers and list them in the DNS Server box. In the above case, the address of the "gateway" is being used, and it simply forwards requests to the default locations it has configured. For a further explanation on using the program, see How DNS Works!.

ADDITIONAL NOTES

ClientDNS supports many different question types, but the 2 most common are "A" records and "PTR" records. PTR requests DO NOT require the use of the reverse INADDR command. The IP address is entered in the normal forward manner, and ClientDNS reformats it.

Notice that ClientDNS defaults to "Recursion Desired" when first activated. When the "Root Servers" button is clicked, it automatically reverts to no recursion since it is not offered by the root servers.

Double clicking on any of the displayed fields will display the field in the bottom line and add it to the clipboard. This feature is useful when drilling down to get to the answer.

UPDATE: (02/15/2011) Version 2 no longer uses the Winsock Control, but uses the Winsock API instead. The IPv6/IPv4 Version is now available.

Back to Top


| Home Page


address