🚀 go-pugleaf

pjm@SPEECH.CS.CMU.EDU (Pedro J. Moreno) writes:

>I have an IP address, and I want to know to what organization
>it corresponds.
>
>What database could I access dor this purpose??


The whois server at nic.ddn.mil will tell you what you want to know.
For example, to look  up the organisation associated with our B Class
network, one would use :-

bambi @ fiddich:/home/bambi> whois -h nic.ddn.mil 131.244 
Bond University (NET-BOND-UN1)
   Cloverdale Drive
   Burleigh Forest
   Queensland 4226
   AUSTRALIA

   Netname: BOND-UN1
   Netnumber: 131.244.0.0

   Coordinator:
      Hughes, David J.  (DJH57)  bambi@BU.OZ.AU
      +61 75 951450

   Domain System inverse mapping provided by:

   KIRK.BU.OZ.AU		131.244.1.1
   SURF.SICS.BU.OZ.AU		131.244.8.20
   CUSCUS.CC.UQ.OZ.AU		130.102.128.43

   Record last updated on 06-Oct-92.



Not only do you get the organisation name but also contact details for
an "informed" person at the site.


   ___                                 David J. Hughes     bambi@bu.oz.au
  /   \                /  /    /        
 /  __/ __   __   ____/  /    / __          Senior Network Programmer
/    \ /  \ /  \ /   /  /    / /  \  /    Comms Development & Operation
\____/ \__//   / \__/   \___/ /   / /       AUSTRALIA  (+61 75 951450)

pjm@SPEECH.CS.CMU.EDU (Pedro J. Moreno) writes:

>Again,   I hope the collective knowledge will have this info.

>I have an IP address, and I want to know to what organization
>it corresponds.

>What database could I access dor this purpose??

You could use nslookup or you could use dig as well probably.  These will
let you interogate the nameserver database to help you to find information
about the sites.

assuming you have the site 1.2.3 which you wish to know, you could find out
the machines in the domain and their names by doing the following

nslookup	(run nslookup)
root		(set server to the root name server)
ls 3.2.1.in-addr.arpa.	(list the machines in this domain and name servers
                         for the same)

This method isn't foolproof as many machines have no reverse name lookup
information.  Also, the root name server may not have any information on
this domain and you will have to find one that does.

I haven't used dig much, but I think it will do similar things.

NOTE:  All these programs will get you is the name of the machine and some
idea of who is above them.  You could probably achieve the same with a
small program that calls gethostbyaddr.  They will not give you info on the
organisation behind the machine, but you can often hazard a guess.  Another
way to find the machine name is to telnet to port 25 and then type quit.
Sendmail lists the full machine name as part of the version string it
prints when you connect (usually)

Craig

--
Craig Richmond.  Computer Officer -  Dept of Economics (morning) 380 3860
  University of Western Australia    Dept of Education (afternoon)
craig@ecel.uwa.edu.au Dvorak Keyboards RULE!  "Messes are only acceptable
if users make them.  Applications aren't allowed this freedom" I.M.VI 2-4

craig@ec.uwa.oz.au (Craig Richmond - division) writes:

>pjm@SPEECH.CS.CMU.EDU (Pedro J. Moreno) writes:

>>I have an IP address, and I want to know to what organization
>>it corresponds.

>You could use nslookup or you could use dig as well probably.  These will
>let you interogate the nameserver database to help you to find information
>about the sites.


I usually get confused about nslookup's syntax, so I look for the 'easy'
ways out.  One is to use the services of netinfo.berkeley.edu on port 117
via telnet (telnet netinfo.berkeley.edu 117).  Dig has proven especially
useful, and is used by the folks at the NIC more than nslookup, it seems.

And then there's a 'simple' (for somebody) trick that you can use in your
login profiles:


alias ptr echo \!$ \| awk -F. \'\{printf \"set q=PTR\\n%s.%s.%s.%s.in-addr.arpa\\n\",\$4,\$3,\$2,\$1\}\' \| nslookup

(If the above lines didn't wrap right, and someone's really interested
in this, let me know and I'll send it over).

Ralph> == Ralph Sims <ralphs@halcyon.com> 

 Ralph> Dig has proven especially useful, and is used by the folks at
 Ralph> the NIC more than nslookup, it seems.

I don't know about the NIC, but I use dig in preference to nslookup.

 Ralph> And then there's a 'simple' (for somebody) trick that you can
 Ralph> use in your login profiles:
[wrapped for clarity]
 Ralph> alias ptr echo \!$ \| awk -F. \'\{printf \"set
 Ralph> q=PTR\\n%s.%s.%s.%s.in-addr.arpa\\n\",\$4,\$3,\$2,\$1\}\' \|
 Ralph> nslookup

The dig equivalent to this is:

alias ptr 'dig -x'

dig is great.  It's on venera.isi.edu, though I don't remember the exact
directory, it should be pretty obvious.

Other nice things about dig come from its nature as a command-line tool;
you can use whatever shell command-line editing you're used to, unlike
with nslookup.

Example: to look up MX records, then HINFO, for a particular machine:

nslookup:
> set q=mx
> foo.bar.dom.
[results]
> set q=hinfo
> foo.bar.dom.
[results]

dig:
% dig foo.bar.dom. mx
[results]
% ^mx^hinfo
[results]

And my favorite dig trick (thanks Randal):
% dig . ns +aa @nearest.root.server > /var/domain/root.cache

Since dig outputs its results in BIND file format (complete with
comments, prefixed with ';') it's great for piping/appending stuff (say,
doing a manual zone transfer to a file so you can prime your secondaries).
--
Christopher K. Davis      | ``Usenet seems to run much like the Kif (or,
<ckd@eff.org>   EFF #14   |   for the TV generation, Klingon) high command.
System Administrator, EFF |   Whoever takes action and can be heard wins.''
+1 617 864 0665  [CKD1]   |   --Peter da Silva <peter@ferranti.com>