Re: [Networker] "nwrecover" results in reverse DNS entry lookup error

On the linux box (i.e. the client) this is the result:

   - Forwared and reverse DNS of itself works
   - Forward DNS of the NetWorker server works
   - Reverse DNS of the NetWorker server does not work

I don't have access to the NetWorker server, but will make sure that this
check is performed there. But I must say that I haven't heard before that
the NetWorker server needs reverse DNS for the client box. But then again,
I'm pretty new to NetWorker. :/



On 11/25/08, Gielisch, Frank <f.gielisch AT w-s-e DOT de> wrote:
>
> What says nslookup!?
> nslookup <server/client name>
> nslookup <server/client IP>
>
> Mit freundlichen Grüßen
>
> Frank Gielisch
> Systemadministrator
>
> Wasserverband Strausberg-Erkner
> Am Wasserwerk 1
> 15344 Strausberg
>
> Tel.: +49 (0) 3341-343-273
> Fax: +49 (0) 3341-343-280
> e-Mail: f.gielisch AT w-s-e DOT de
>
>
>
> -----Ursprüngliche Nachricht-----
> Von: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] Im
> Auftrag von Kenneth Holter
> Gesendet: Dienstag, 25. November 2008 10:39
> An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Betreff: Re: [Networker] "nwrecover" results in reverse DNS entry lookup
> error
>
> Oh, so both my RHEL 5.1 box and the NetWorker server need reverse DNS on
> both itself as well as the other one? In other words, my linux box need
> reverse DNS lookup of itself and the NetWorker server, and the NetWorker
> server need reverse DNS lookup of itself and the linux box?
>
> In the linux box, the NetWorker servers are already added to the /etc/hosts
> file (btw, which tools can I use to verify reverse entries when such
> entries
> are added to this file), and the DNS server supports reverse DNS of itself.
>
>
> On 11/25/08, Gielisch, Frank <f.gielisch AT w-s-e DOT de> wrote:
> >
> > DNS have to work for both clients.
> > if you have problems with DNS, try to edit the hosts files (/etc/hosts)
> of
> > both clients.
> >
> >
> > regards
> >
> >
> > -----Ursprüngliche Nachricht-----
> > Von: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] 
> > Im
> > Auftrag von Kenneth Holter
> > Gesendet: Dienstag, 25. November 2008 10:14
> > An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Betreff: Re: [Networker] "nwrecover" results in reverse DNS entry lookup
> > error
> >
> > Thanks for the replies.
> >
> > My /nsr/res/servers file already contains the names of the NetWorker
> > servers.
> >
> > I forgot to mention that the reverse DNS example in my first posts shows
> > reverse DNS entires for the host I'm performing the recovery on. So for
> > this
> > host the reverse DNS seems to work fine. But does reverse DNS have to
> work
> > for the NetWorker servers also?
> >
> >
> > On 11/25/08, Gielisch, Frank <f.gielisch AT w-s-e DOT de> wrote:
> > >
> > > Try to edit the "servers" file in /nsr/res/.  Put the name or the ip
> from
> > > the networker server in this file.
> > >
> > > Regards
> > > FG
> > >
> > >
> > > -----Ursprüngliche Nachricht-----
> > > Von: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT 
> > > EDU]
> Im
> > > Auftrag von Kenneth Holter
> > > Gesendet: Dienstag, 25. November 2008 08:40
> > > An: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > > Betreff: [Networker] "nwrecover" results in reverse DNS entry lookup
> > error
> > >
> > > Hi.
> > >
> > >
> > > I need to recover a file on my RHEL 5.1 box, and try and start up
> > > "nwrecover" to do this. When I issue the command ("nwrecover") I get an
> > > error message saying that "Unable to establish connection to a network
> > > server. Error returned: Host name verification failed - unknown host:
> > > 1.2.3.4, please check reverse lookup entry for this machine on your
> name
> > > server".
> > >
> > > The commands "host server AT example DOT com" returns "1.2.3.4", and "host
> > > 1.2.3.4"
> > > returns "server AT example DOT com". So too me everything looks fine.
> > >
> > > Does anyone know what may be causing this error?
> > >
> > >
> > > Regards,
> > > Kenneth Holter
> > >
> > > To sign off this list, send email to listserv AT listserv.temple DOT edu 
> > > and
> > type
> > > "signoff networker" in the body of the email. Please write to
> > > networker-request AT listserv.temple DOT edu if you have any problems with
> this
> > > list. You can access the archives at
> > > http://listserv.temple.edu/archives/networker.html or
> > > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> >
> > To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type
> > "signoff networker" in the body of the email. Please write to
> > networker-request AT listserv.temple DOT edu if you have any problems with 
> > this
> > list. You can access the archives at
> > http://listserv.temple.edu/archives/networker.html or
> > via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and 
> type
> "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with 
> this
> list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or
> via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>

To sign off this list, send email to listserv AT listserv.temple DOT edu and 
type "signoff networker" in the body of the email. Please write to 
networker-request AT listserv.temple DOT edu if you have any problems with this 
list. You can access the archives at 
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER