Networker

Re: [Networker] Client Addition bug in 6.1.3

2003-07-14 07:09:12
Subject: Re: [Networker] Client Addition bug in 6.1.3
From: Davina Treiber <Treiber AT HOTPOP DOT COM>
To: NETWORKER AT LISTMAIL.TEMPLE DOT EDU
Date: Mon, 14 Jul 2003 07:59:39 +0100
Joel Fisher wrote:
It wasn't a problem with my environment until upgrading to 6.x.

Not sure why nslookup is considered unreliable when used to query
internal DNS entries.  But I'll verify that getent returns the proper
entries when I have a problem adding my next client.  However, if it was
a DNS issue then it would stop working again once I removed the
/etc/hosts entry from my server, but after that initial backup
everything works perfectly.

Back to basics on Solaris admin here...

I assume that the reason that the other respondent said that nslookup
was unreliable in this sense was that it only checks that you CAN
resolve the address using the DNS. What it doesn't check is that Solaris
and applications will actually use it. You could have a 100% working DNS
but Solaris would still ignore it if the hosts line in nsswitch.conf
wasn't set to use DNS.

I would hazard a guess that the bug here is related to the internal
caching of IP addresses in 6.1.3. Once NetWorker has picked up the
address from somewhere (/etc/hosts in this case) it will keep on working.

All this said, Legato have said in this thread that it is down to a
known bug, so that's our answer.

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listmail.temple DOT edu or visit the list's Web site at
http://listmail.temple.edu/archives/networker.html where you can
also view and post messages to the list.
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=