Nslookup is a program to query Internet domain name servers.
Nslookup has two modes: interactive and non-interactive.
Interactive mode allows the user to query name servers for
information about various hosts and
domains or to print a list of hosts in a domain. Non-interactive
mode is used to print just the name and requested information
for a host or do
IPv4 Address (32 bits)
Mail Exchange Record
IPv6 Address (128
Request for Zone
Request for All
Using nslookup from
In windows just open the command prompt and type nslookup
In *nix bsed systems open the terminal window and type nslookup
220.127.116.11.in-addr.arpa host name = ccug.ser.ac.uk
DNS Records Explanation
A simple query for the IP address corresponding to
A given host can have several DNS names. One of these is the
canonical or reference name. This query reveals that
www.ser.ac.uk is really ccuf.ser.ac.uk.
A mail exchanger query, this time for the domain ser.ac.uk which
reveals that mail sent to email@example.com is actually sent to
18.104.22.168 which is really ccug.ser.ac.uk. (see below).
An HINFO query. This is only useful if the DNS domain
administrator has bothered to create the relevant records and
keep them up to date.
A PTR query. This shows "inverse" or "reverse" resolution.
Notice the very clumsy way the query has to be entered, this is
partly because IP addresses have the most sigificant part first
whereas DNS addresses have the most significant part last. There
are plenty of pieces of software that do reverse resolution
without this clumsy interface.
The host you queried can not be resolved using the current DNS
server. If the current DNS server is not the source of authority
for the domain in question, you should locate the SOA DNS server
and try querying that host directly for information on the
*** No <record type> information is available for <hostname>
No such record type appears in the DNS system for the hostname
you are querying. Again, try the SOA DNS server is you have
*** Request to <server> timed-out
The server which was specified with the last 'server' command is
not accepting DNS queries. Either it is not up and running on
the network, or it is not accepting packets on the DNS channel.