Hi guys:
I've got my setup working nicely.
My 'amdumps' are working lovely and I can log onto *almost* every
server to restore.
Here is my problem:

I've got multi-homed servers straddling half a dozen subnets. So
nslookup for me is a bit tricky. In the example presented below - this
host resolves to both of it's IP_ADDR to it's true hostname. But since
the traffic isn't going through the interface that has precedence via
my DNS the recover fails.

I read in the documents that:
=============================
If the tape server has multiple network connections, an amanda.conf 
interface section may be set up for each one and clients allocated to
a particular interface with field five of the disklist. Individual
interfaces take precedence over the general netusage  bandwidth limit
and follow the same guidelines described above in "Configuring
Amanda": the limit is imposed when deciding whether to start a dump,
but once a dump starts, Amanda  lets underlying network components do
any throttling.

Individual Amanda interface definitions do not control which physical
connection is used. That is left up to the operating system network
software. While it's common to give an Amanda interface definition the
same name as a physical connection, e.g. le0, it might be better to
use logical names such as back-door-atm to avoid confusion.
=============================

But this doesn't seem to address my issue.
Is there anywhere that you can specify which interface to connect on a
per/machine basis?
Has anyone had a similar experience?

*an aside:
Why do the amdumps never work for directories on the tape_host itself?
I always get time out errors on the tape_host when running amcheck,
the 'results missing' for the reports (duh) as it fails to backup the
disklist entry I've got.
--------
vega.scarceskills.com   /home/data/amanda       holding-disk    -1      local
vega.scarceskills.com   /etc                               full_dump  
    -1      local
--------
-Peter Farrell
Below is an example of the failure I'm talking about:


[root@test root]# /usr/local/amanda/sbin/amrecover misc_backups
AMRECOVER Version 2.4.5p1. Contacting server on amanda ...
220 vega AMANDA index server (2.4.5p1) ready.
500 Access not allowed: [ip address 192.168.2.6 is not in the ip list
for test.example.com]

[root@test root]# nslookup 192.168.2.6
Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server:         192.168.2.1
Address:        192.168.2.1#53

6.2.168.192.in-addr.arpa        name = test.example.com.

[root@test root]# nslookup test.example.com
Note:  nslookup is deprecated and may be removed from future releases.
Consider using the `dig' or `host' programs instead.  Run nslookup with
the `-sil[ent]' option to prevent this message from appearing.
Server:         192.168.2.1
Address:        192.168.2.1#53

Name:   test.example.com
Address: 192.168.1.12

[root@test root]# ifconfig eth0
eth0      Link encap:Ethernet  HWaddr 00:C0:9F:24:13:69
          inet addr:192.168.2.6  Bcast:192.168.2.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:148739640 errors:0 dropped:0 overruns:0 frame:0
          TX packets:148802007 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          RX bytes:346460140 (330.4 Mb)  TX bytes:2200857768 (2098.9 Mb)
          Interrupt:10 Base address:0xecc0 Memory:fe100000-fe120000

[root@test root]# ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:40:F4:38:F0:0B
          inet addr:192.168.1.12  Bcast:192.168.1.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:16039942 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16286994 errors:7 dropped:0 overruns:7 carrier:7
          collisions:0 txqueuelen:100
          RX bytes:2960583231 (2823.4 Mb)  TX bytes:181414560 (173.0 Mb)
          Interrupt:5 Base address:0x4000