2: nslookup 4.1.3

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_

                                                            

  Sean Harvey OAO Corp harvey@nmc8.chinalake.navy.mil

     Ridgecrest CA (619)939-2199

                                                            

        Knowledge is a process of piling up facts;

           wisdom lies in their simplification.

\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_\_


Original posting:

> Dear friends-

>

> I can't do a reverse nslookup on any SunOS 4.1.3 machine. Here is what I

> get when I use the command under Solaris 2.5.1. It works:

>

> nmc13% nslookup 199.120.150.1

> Server: sunman.chinalake.navy.mil

> Address: 129.131.1.189

>

> Name: owens.ridgecrest.ca.us

> Address: 199.120.150.1

>

>

>

> When I try the same command on a SunOS machine, I get this. It doesn't

> return the domain name:

>

>

> nmc8:/tmp_mnt/u/harvey> nslookup 199.120.150.1

> Server: chinalake.navy.mil

> Address: 129.131.1.189

>

> Name: [199.120.150.1]

> Address: 199.120.150.1

>

>

>

> My question is whether I have a config problem or whether this command

> is not supported under SunOS. Thanks in advance.

>

> Sean

>

I have already posted my summary but I felt it my duty to repost since Peter Allen has sent me an nslookup file that works under 4.1.3 with no fiddling around:

nslookup 123.456.789.xxx

returns the DNS name

If anyone would like this file I will forward it on to you.

Sean

==================

From:peter.allan@aeat.co.uk (Peter M Allan)

To:harvey@nmc8.chinalake.navy.mil

Subject: reverse nslookup SunOS fails

Sean,

When my nslookup stopped behaving I asked our

internet support people and they had upgraded

their nameservers without telling us. They

were able to point me to a new nslookup

program that works fine in the new scheme.

========================================================

Also ....

From: Bob Woodward <bobw@www.filmworks.com>

Subject: Re: reverse nslookup SunOS fails

Mime-Version: 1.0

Content-Type: text/plain; charset="us-ascii"

Sounds to me like you have a DNS problem. There are three 'main' files in

DNS. One is the cache file, one is used for name to IP lookups and one is

used for IP to name lookups. On our system these files are

/var/named/db.cache, /var/named/db.filmworks, and /var/named/db.207.82.202.

 There should be an entry in the third one that has your system name in it.

 It is possible that the name in that file is "[199.120.150.1]" instead of

a system name. Some admins might do this to help them track which IP

numbers have been assigned and which ones have not.

You're file names may be different and/or in different locations. You need

to get ahold of the 'DNS and BIND' book from O'Reilly and Associates.

===========================================

It's easier to use the "host" command, which comes with the latest BIND

   distributions.

        % host 199.120.150.1

        Name: owens.ridgecrest.ca.us

        Address: 199.120.150.1

        Aliases:

   Bind is at:

        ftp://ftp.vix.com/pub/bind/release/4.9.5/bind-4.9.5-REL.tar.gz


--
Karl Vogel vogelke@c17.wpafb.af.mil

[5764 byte] By [CodeProf.com] at [2007-12-25 10:03:00]