Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!hplabs!hpcc05!hpcc01!cricket
From: cricket@hpcc01.HP.COM (Cricket Liu)
Newsgroups: comp.sys.hp
Subject: Re: nslookup changes names
Message-ID: <1670016@hpcc01.HP.COM>
Date: 16 Apr 91 02:06:20 GMT
References: <1991Apr12.162911.15088@aio.jsc.nasa.gov>
Organization: the Mosthamster's Desk, Internet Engineering
Lines: 40


    When I start nslookup, sometimes the default server is listed as the
    new name of the machine (good) and sometimes it is listed as the old
    name (bad).  I've deleted all references to the old name that I can
    find.  I have done a grep of every file in /etc, /usr, /, /lib, and
    /usr/etc.  I have also done grep on the entire disk (except for FIFO's
    & such).  I can't find the old name anywhere.

I think that's because the name isn't on your system anymore - it's on
sweetpea.jsc.nasa.gov and nameserver.arc.nasa.gov, both supposedly
118.134.in-addr.arpa name servers.

nslookup gets the name to put in its banner by mapping the IP address of
the local host back to a domain name, which translates (in deltahp's case)
to a query for a PTR record attached to 8.141.118.134.in-addr.arpa.  jesnic
has the correct answer - deltahp.jsc.nasa.gov - but sweetpea and nameserver
show the old name.

It *looks* by your name servers like jesnic.jsc.nasa.gov is the primary for
118.134.in-addr.arpa, and sweetpea and nameserver are secondaries.  But 
only nameserver seems to be authoritative for the domain:  the TTLs on the 
PTR record keep decrementing on sweetpea, and they differ from the record 
on the primary.  However, nameserver reports that only jesnic is authoritative 
for 118.134.in-addr.arpa, but the root name servers report that all three
should be.

So to sum it all up, it looks like nameserver thinks it's authoritative for
118.134.in-addr.arpa but isn't in synch with jesnic, while sweetpea doesn't
think it's authoritative for 118.134.in-addr.arpa at all.  Look to see
whether nameserver thinks it's primary when it should be secondary, and
also make sure that the serial number of 118.134.in-addr.arpa on jesnic has
changed so nameserver knows to zone transfer the new database.  And either
configure sweetpea to load 118.134.in-addr.arpa from jesnic, or update your
delegation information with the NIC to delete the delegation to sweetpea.

Feel free to contact me if I haven't been clear enough.

cricket

hostmaster@hp.com