Purpose of this tool:
- The purpose of this tool is to
give you a set of tools for querying a DNS for specific resource
records or sets of resource records. It also gives
you two tools for querying the DNS assigned to your
computer through DHCP or other means and it gives
you a tool for clearing the cache used by your
default DNS.
Tool Capabilities - Simple Query using your default
DNS
Watch a demonstration video of Simple Query in the Overview
Video.Simple Query.
This tool uses your operating system's built-in resolver
to do a basic DNS query. It accepts an IPv4 address or hostname
and queries your default name servers for the translation.
Your operating system may also attempt to determine the
NetBIOS computer name if the default DNS fails to respond
to an IP address query. Both IPv4 and IPv6 are
supported, but you need an IPv6 capable operating system
like Windows 7 or Vista to do IPv6 queries.
[Start Query]
Looking up [www.facebook.com]
Hostname: www.facebook.com
IP Address: 69.171.228.40
Timestamp: 11/07/11 16:56:14
[End Query]
[Start Query]
Looking up [www.v6.facebook.com]
Response #1:
IPv6 address: 2620:0:1cfe:face:b00c::3
Timestamp: 11/07/11 16:54:54
[End Query]
Tool Capabilities - Who Am I and Test Default Servers
Watch a demonstration video of "Who Am I" in the Overview
Video.Who Am I?
This button asks queries your system for it's Windows computer
name. Then it uses that name to obtain the IP addresses
and any aliases assigned to your computer. It shows the
list of default DNS name servers used by your computer.
This Computer's Name and IP Address:
Hostname: OldDell
IP Address: 192.168.0.58
Domain Name:
DNS Server IP Address(es):
208.200.248.1
208.200.248.8
Watch a demonstration video (flash) of Test Default Servers
in the Overview Video.
Test Default Servers. This tool
takes an IP address or hostname and requests the A or PTR
record from each DNS name server assigned to your computer.
This tells you if each default DNS is working or communicating
properly when a simple name resolution query is made by
any internet enabled program.
Test of each Default DNS using
an 'A' record query for microsoft.com
Starting Timestamp: 01/21/09 11:25:45
Testing 208.200.248.1
Server Reply Code: No Error.
Server can do recursion.
A Record: 207.46.232.182
A Record: 207.46.197.32
Server Response Time = 0.047 seconds
Testing 208.200.248.8
Server Reply Code: No Error.
Server can do recursion.
A Record: 207.46.232.182
A Record: 207.46.197.32
Server Response Time = 0.078 seconds
NSLOOKUP (Name Server Lookup)
Watch a demonstration video (flash) of NSLOOKUP used to
get resource records for a domain.
Watch a demonstration video (flash) of DiG +trace and NSLOOKUP
used to get resource records for an IP address.
NSLOOKUP. This
tool functions like the UNIX or Windows command line nslookup
program. It uses the parameters specified in Setup to define
which records are requested from DNS. Unlike Simple Query,
you can specify exactly which DNS server to use with your
NSLOOKUP, AXFR, or DIG queries -- the DNS can be anywhere
reachable through the network. We support 47 record types
including the popular A, ANY, CNAME, MX, NS, PTR, SOA, and
TXT types. A typical 'ANY' query result is shown below:

DiG (Domain Information Groper)
Watch a demonstration video (flash) of DiG and DiG +trace.
DiG (Domain Information Groper)
is similar in functionality to NSLOOKUP, however, it provides
much more detailed information. Our current output format
is based on Dig version 9.x.

Watch a demonstration video (flash) of DiG +trace and NSLOOKUP
used to get resource records for an IP address.
Watch a demonstration video (flash) of DiG and DiG +trace.
DiG +trace
provides a traceback to the root servers of all delegated
zone responsible name servers down to the authoritative
host for the domain or IP address you entered. This example
shows a query of nwpsw.com.
[Start Query]
DiG Starting Timestamp: 01/21/09 11:32:42
; <<>> DiG 9.x <<>> nwpsw.com +trace
. 423436 IN NS K.ROOT-SERVERS.NET
. 423436 IN NS J.ROOT-SERVERS.NET
. 423436 IN NS M.ROOT-SERVERS.NET
. 423436 IN NS B.ROOT-SERVERS.NET
. 423436 IN NS H.ROOT-SERVERS.NET
. 423436 IN NS L.ROOT-SERVERS.NET
. 423436 IN NS A.ROOT-SERVERS.NET
. 423436 IN NS I.ROOT-SERVERS.NET
. 423436 IN NS C.ROOT-SERVERS.NET
. 423436 IN NS F.ROOT-SERVERS.NET
. 423436 IN NS G.ROOT-SERVERS.NET
. 423436 IN NS D.ROOT-SERVERS.NET
. 423436 IN NS E.ROOT-SERVERS.NET
;; Received 228 bytes from 208.200.248.8 (208.200.248.8)
in 62 ms
com. 172800 IN NS a.gtld-servers.net
com. 172800 IN NS b.gtld-servers.net
com. 172800 IN NS c.gtld-servers.net
com. 172800 IN NS d.gtld-servers.net
com. 172800 IN NS e.gtld-servers.net
com. 172800 IN NS f.gtld-servers.net
com. 172800 IN NS g.gtld-servers.net
com. 172800 IN NS h.gtld-servers.net
com. 172800 IN NS i.gtld-servers.net
com. 172800 IN NS j.gtld-servers.net
com. 172800 IN NS k.gtld-servers.net
com. 172800 IN NS l.gtld-servers.net
com. 172800 IN NS m.gtld-servers.net
;; Received 509 bytes from K.ROOT-SERVERS.NET (193.0.14.129)
in 203 ms
nwpsw.com. 172800 IN NS ns100.apollohosting.com
nwpsw.com. 172800 IN NS ns101.apollohosting.com
;; Received 113 bytes from a.gtld-servers.net (192.5.6.30)
in 219 ms
nwpsw.com. 86400 IN SOA ns100.apollohosting.com nstadmin.sampledomain.com
2009010901l 10800l 3600l 604800l 10800l
nwpsw.com. 86400 IN NS ns100.apollohosting.com
nwpsw.com. 86400 IN NS ns101.apollohosting.com
nwpsw.com. 86400 IN A 74.126.192.136
nwpsw.com. 86400 IN MX mailboxcop.com
;; Received 213 bytes from ns100.apollohosting.com (66.242.27.250)
in 219 ms
[End Query]
Zone Transfer (Automatic or Manual)
This tool can show all the devices
registered in a DNS zone that defines a domain using a
'zone transfer' request. We provide
two types of Zone Transfer: one attempts to automatically
locate the Authoritative host to make the transfer possible
and the other allows you to specify the Authoritative DNS
for the Zone. DNS servers that implement tight security will
not allow you to do a zone transfer unless you are on an
approved IP address list. Transfer method is TCP using AXFR
DNS protocol.
Get Basic DNS Records
This tool retrieves a set of DNS
records from the Current DNS Server all at once. The
records we request are A, AAAA, NS, MX, CNAME, PTR, and
TXT. [Start
Query]
Starting Timestamp: 11/07/11 17:11:50
Basic DNS Records for google.com
Source DNS: 8.8.8.8
Requesting SOA (start of zone authority) Record
google.com. 86399 IN SOA ns1.google.com
dns-admin.google.com 2011110200l 7200l 1800l 1209600l
300l
Requesting A (IPv4 address) Record
google.com. 295 IN A 74.125.53.106
google.com. 295 IN A 74.125.53.104
google.com. 295 IN A 74.125.53.105
google.com. 295 IN A 74.125.53.103
google.com. 295 IN A 74.125.53.99
google.com. 295 IN A 74.125.53.147
Requesting AAAA (IPv6 address) Record
DNS did not have an answer to our request.
Requesting NS (name server) Record
google.com. 37485 IN NS ns2.google.com
google.com. 37485 IN NS ns3.google.com
google.com. 37485 IN NS ns1.google.com
google.com. 37485 IN NS ns4.google.com
Requesting MX (mail exchange) Record
google.com. 600 IN MX alt4.aspmx.l.google.com
google.com. 600 IN MX alt1.aspmx.l.google.com
google.com. 600 IN MX alt3.aspmx.l.google.com
google.com. 600 IN MX alt2.aspmx.l.google.com
google.com. 600 IN MX aspmx.l.google.com
Requesting CNAME (host alias name) Record
DNS did not have an answer to our request.
Requesting PTR (pointer) Record
DNS did not have an answer to our request.
Requesting TXT (general text) Record
google.com. 3600 IN TXT v=spf1
include:_netblocks.google.com ip4:216.73.93.70/31
ip4:216.73.93.72/31 ~all
[End Query]
Hosts File Editor and Flush Default DNS Cache
Two additional parts of DNS Tools - Core
are the Hosts File Editor and Flush Default DNS Cache.
The Hosts file is used by Windows (and
other operating systems) as a local database for
resolving hostnames to IP addresses and vice versa. If
something is in the hosts file, TCP/IP uses the
information found in the hosts file instead of querying
DNS. The hosts file is a simple text file and we have
provided an editor to help you manage it.
Flush Default DNS Cache does what it
says - it clears your local cache of IP addresses and
hostnames that were recently resolved. It accomplishes
exactly the same thing as doing ipconfig /flushdns from
the command line. This only affects names and IPs
resolved by your TCP/IP networking subsystem, it does
not affect anything resolved using our nslookup or dig
tools.