>  
> > Ideally, each network connection on any system on your network will  
> > have its own DNS entry. If that's the
> > case, just create a client resource that refers to the DNS entry for  
> > the client's backup network address.
>  
>  That's what I tried before, and it did not work.

No, it will not be enough as the nsrexecd on the client will ask
it's host "Where am I running" and then get the Primary network name
as answer.
In later communication with the Networker server this is the name it
will report back, disregarding the interface name for the IP-traffic.

This is why you need to alias the primary name to the right client.
Then Networker knows that it is OK that a client called clinet1-backup
is calling itself client1 and associate the indexes in the right way.

Dag

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
wit 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